Canadian Crosscompile: cc1: error: unrecognized option `-Wold-styl e-definition'

Dan Kegel
Tue Oct 5 05:37:00 GMT 2004

Alexander Povolotsky wrote:
> HEADERS="ansidecl.h" DEFINES="" \
> /bin/sh /cygdrive/d/Profiles/apovolot/crosstool/crosstool-0.28-rc36/build/powerp
> c-860-linux-gnu/gcc-3.4.1-glibc-2.3.3/gcc-3.4.1/gcc/ tconfig.h
> echo '#define FLOAT' > fp-bit.c
> cat /cygdrive/d/Profiles/apovolot/crosstool/crosstool-0.28-rc36/build/powerpc-86
> 0-linux-gnu/gcc-3.4.1-glibc-2.3.3/gcc-3.4.1/gcc/config/fp-bit.c >> fp-bit.c
> cat /cygdrive/d/Profiles/apovolot/crosstool/crosstool-0.28-rc36/build/powerpc-86
> 0-linux-gnu/gcc-3.4.1-glibc-2.3.3/gcc-3.4.1/gcc/config/fp-bit.c > dp-bit.c
> powerpc-860-linux-gnu-gcc -O2 -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-string
> s -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./in
> clude  -I. -I. -I/cygdrive/d/Profiles/apovolot/crosstool/crosstool-0.28-rc36/bui
> ld/powerpc-860-linux-gnu/gcc-3.4.1-glibc-2.3.3/gcc-3.4.1/gcc -I/cygdrive/d/Profi
> les/apovolot/crosstool/crosstool-0.28-rc36/build/powerpc-860-linux-gnu/gcc-3.4.1
> -glibc-2.3.3/gcc-3.4.1/gcc/. -I/cygdrive/d/Profiles/apovolot/crosstool/crosstool
> -0.28-rc36/build/powerpc-860-linux-gnu/gcc-3.4.1-glibc-2.3.3/gcc-3.4.1/gcc/../in
> clude   -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-
> zero-initialized-in-bss -fno-unit-at-a-time -msdata=none \
>   -Dinhibit_libc -c /cygdrive/d/Profiles/apovolot/crosstool/crosstool-0.28-rc36/
> build/powerpc-860-linux-gnu/gcc-3.4.1-glibc-2.3.3/gcc-3.4.1/gcc/crtstuff.c -DCRT
> _BEGIN \
>   -o crtbegin.o
> cc1: error: unrecognized option `-Wold-style-definition'
> cc1: error: unrecognized option `-fno-unit-at-a-time'
> make[1]: *** [crtbegin.o] Error 1
> make[1]: Leaving directory `/cygdrive/d/Profiles/apovolot/crosstool/crosstool-0.
> 28-rc36/build/powerpc-860-linux-gnu/gcc-3.4.1-glibc-2.3.3/build-gcc-core/gcc'
> make: *** [all-gcc] Error 2

I don't fully understand gcc's build process, but I get the
feeling that you might be better off building the crosscompiler
with crosstool using the same sources as you plan to build
the target compiler with.  That should certainly get around
this problem.  Or are you particularly devoted to your existing
- Dan

My technical stuff:
My politics: see for examples of why I'm for regime change

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list