--- Comment #6 from pinskia at gcc dot gnu dot org 2010-01-19 02:45 ---
>They are inconsistent, right?
No because i386-driver.c is only supposed to be compiled with a x86 or x86_64
compiler. Really the file could have
#if !defined(__i386__) && !defined(__x86_64__)
#error "This should o
--- Comment #5 from monaka at monami-software dot com 2010-01-19 02:42
---
(In reply to comment #3)
> driver-i386.c should not be included if you are compiling for a PPC host/build
> really. So it is a problem of you misconfiguring GCC really and nothing else.
I see what you want to s
--- Comment #4 from pinskia at gcc dot gnu dot org 2010-01-19 00:13 ---
More to the point, use lipo to combine the gcc drivers after the fact to get a
dual arch executable.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42785
--- Comment #3 from pinskia at gcc dot gnu dot org 2010-01-19 00:10 ---
driver-i386.c should not be included if you are compiling for a PPC host/build
really. So it is a problem of you misconfiguring GCC really and nothing else.
--
pinskia at gcc dot gnu dot org changed:
--- Comment #2 from monaka at monami-software dot com 2010-01-18 23:29
---
(In reply to comment #1)
> If you use -arch ppc, then the host/build is really powerpc-apple-darwin so
> obviously you are configuring GCC incorrectly and the error message is correct
> as that is x86 inline-asm
