-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
target tuples for solaris not quite right #40531
Copy link
Copy link
Closed
Labels
A-target-specsArea: Compile-target specificationsArea: Compile-target specificationsC-bugCategory: This is a bug.Category: This is a bug.O-solarisOperating system: SolarisOperating system: SolarisT-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Metadata
Metadata
Assignees
Labels
A-target-specsArea: Compile-target specificationsArea: Compile-target specificationsC-bugCategory: This is a bug.Category: This is a bug.O-solarisOperating system: SolarisOperating system: SolarisT-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Type
Fields
Give feedbackNo fields configured for issues without a type.
There are actually two different generally expected encodings of the host tuple and they're subtly different than what some might expect.
For example, 'x86_64-sun-solaris' should probably be x86_64-pc-solaris. The reason for that is that the encoding schemes are actually:
https://github.com/gcc-mirror/gcc/blob/master/config.sub
So while 'sparcv9-sun-solaris' is correct because Sun is the (historical) manufacturer of sparc CPUs, 'x86_64-sun-solaris' is not, because the MANUFACTURER here is the manufacturer of the CPU not the operating system. There are special cases for this, for example 'x86_64-apple-darwin', even though Apple doesn't make x86_64 CPUs, but following gcc/clang conventions leads us to x86_64-pc-solaris.
This issue has been assigned to @lzutao via this comment.