Summary: | sys-kernel/linux-headers does not recognize CHOST="pentium3-pc-linux-gnu" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gordon Schumacher <gordons> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | minor | CC: | jer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/doc/en/change-chost.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gordon Schumacher
2009-02-13 22:53:40 UTC
Set CFLAGS for (sub)architecture specific optimisations. CHOST has no influence on those whatsoever. Unless I'm horribly mistaken, this is not true for the more heavily-optimized packages such as gmp, mpfr, and some of the multimedia libs. I do know that, for instance, gmp has multiple sets of optimized assembly routines for different specific flavours of x86, and uses the string passed to --host to determine which to use. Thus, "./configure --host=pentium3-pc-linux-gnu" will use assembly routines utilizing sse, but "./configure --host=i686-pc-linux-gnu" will not. In my particular situation, I am building an environment that has a minimum system requirement of a Pentium 3 processor, hence why I changed CHOST. I was worried about changing CHOST for just those packages - I was afraid that might cause library-linking issues, so I simply changed it in make.conf; perhaps that's not the correct answer here. Your CHOST is not valid (there's a canonical list somewhere) GMP chooses optimizations based on the CPU yes, and it's wrongly doing so based on the CHOST setting. It needs to export that ability further out. If you can find packages where it's automatically using the CHOST to decide on optimizations, please file a bug for each of those packages. Closing now, please report seperate bugs for each badly behaved package like GMP is doing with detection based on CHOST. (It can cause issues when you're building between machines easily). no, dont report any bugs at all about CHOST=pentium3-xxx. that is not a valid chost. the gmp issue is completely isolated and there is a bug open dealing with that. vapier: you mis-interpreted what I said. To clarify, if there are packages doing detection of what to build based on invalid CHOST strings (like pentium3-...), those packages need to be fixed. not really ... in the case of gmp, it does extra special magic. look at the bug open about it. |