This patch disables checks for presence of MMX, 3DNOW, all SSE, and AVX in Qt configurator on PPC host Reproducible: Always
Created attachment 255043 [details, diff] Patch for qt4-build.eclass
This modification should really work for any x86 incompatible arch
Maybe we should add USE flags for the different instruction sets instead, and mask them where unsupported? I think this is a requirement for proper cross-compilation support.
Maybe CTARGET could be used instead of CHOST?
I think the best option would be something like "if CTARGET != {list of all x86-compatible archs} ..."
CTARGET is wrong. You're mixing the definitions, see http://blog.flameeyes.eu/2008/08/10/autotools-targets-and-hosts for a brief explanation.
OK, we could use CHOST when we are not cross-compiling, or CTARGET when we do
(In reply to comment #7) > OK, we could use CHOST when we are not cross-compiling, or CTARGET when we do > CTARGET is still wrong. CHOST is always the machine you are building *for*, CBUILD is the current machine. You always want to use CHOST to determine the machine the program/library/etc. to be used on. CTARGET is only used for things like compilers, which can be built on one machine, used on another, and produce code for a third (CBUILD is the machine building the compiler, CHOST is the machine running it, and CTARGET is the machine the output of that compiler will be used on). If the package is not a compiler (or something similar, such as binutils), then you want to use CHOST.
Thanks for explanation!
Why should we do this? Does checking for unsupported instruction sets cause any problems on ppc?
Closing as WONTFIX, I'll reopen if you can provide a valid argument to disable such checks.
