This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
cc1: error: invalid option `powerpc' cc1: error: invalid option `new-mnemonics'
This 'gcc' should put your bells ringing... Isn't it your native GCC which doesn't know anything about the '-mpowerpc' and '-mnew-mnemonics' options? A Linux/PPC targeted GCC surely knows these...
*** errlist.c count 1 vs Versions sys_errlist@GLIBC_2.3 count 126
make[2]: *** [/export/home/jdubois/crosstool-0.28-pre7/build/powerpc-7400-linux-
gnu/gcc-3.3.2-glibc-2.3.2/build-glibc-headers/stdio-common/errlist-compat.c] Err
or 1
make[1]: Leaving directory `/export/home/jdubois/crosstool-0.28-pre7/build/power
pc-7400-linux-gnu/gcc-3.3.2-glibc-2.3.2/glibc-2.3.2'
You cannot build glibc-2.3.2 using your native GCC, you must use a Linux/PPC targeted GCC !
He knows that. If you check the log against crosstool.sh, you'll see he's only trying to install glibc's headers, and for some reason, the workaround I did to force glibc to not compile anything while doing that isn't working for him. So I need a more robust way to install the glibc headers needed to compile the gcc-3.3.x bootstrap compiler. - Dan
-- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |