| Summary: | toolchain-funcs.eclass does not handle amd64-* tuples | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sven E. <dark> |
| Component: | Eclasses | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sven E.
2016-04-05 23:16:11 UTC
i'm assuming you meant CHOST and not ARCH, and you're referring to the tc-arch & tc-arch-kernel funcs which parse it via tc-ninja_magic_to_arch while it's true the gnuconfig (config.sub) file accepts amd64-* tuples and rewrites them to x86_64, i don't see any value in supporting that in Gentoo. what use cases do you have to warrant this ? seems like pointless pain when 99.9% of the rest of the world uses x86_64-* tuples. Erh, yes, I indeed meant the part in in ninja_magic_to arch. I consider it rather a question of completness and choice. Anyhow, if it is not supported and won't be supported, I assume it is at least documented properly somewhere? (In reply to Sven E. from comment #2) the "choice" part is kind of specious don't you think ? as for documentation, i'm not sure what you're looking for ... all Gentoo stages ever released by the project have used x86_64-* tuples. all of our profiles default to x86_64-*. all of our tools have only ever used x86_64-*. it's pretty unlikely you'd use amd64-* by accident. listing it in any documentation would serve just to confuse people rather than contribute anything useful imo. |
