I want to set up a compile tool chain for my Raspberry pi. But,when I run: # crossdev -S -v -t armv6j-hardfloat-linux-gnueabi it failed with message: failed to configure glibc Reproducible: Always Steps to Reproduce: 1. emerge sys-devel/crossdev 2. crossdev -S -v -t armv6j-hardfloat-linux-gnueabi 3. Actual Results: Failed to configure glibc
Created attachment 334688 [details] cross-armv6j-hardfloat-linux-gnueabi-info.log
Created attachment 334692 [details] cross-armv6j-hardfloat-linux-gnueabi-glibc.log
Created attachment 334694 [details] emerge-info.txt
Created attachment 334696 [details] /var/tmp/portage/cross-armv6j-hardfloat-linux-gnueabi/glibc-2.15-r3/work/build-default-armv6j-hardfloat-linux-gnueabi-nptl/config.log In the config.log file a find this error: ... /usr/bin/uname -p = Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz /bin/uname -X = unknown ... configure:2760: $? = 1 configure:2765: checking for suffix of object files configure:2787: armv6j-hardfloat-linux-gnueabi-gcc -c -march=core2 -pipe -O2 -fno-strict-aliasing -U_FORTIFY_SOURCE -U_FORTIFY_SOURCE -U_FORTIFY_SOURCE conftest.c >&5 Assembler messages: Error: unknown architecture `core2' Error: unrecognized option -march=core2 conftest.c:1:0: error: bad value (core2) for -march= switch configure:2791: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "GNU C Library" ...
Try removing the partially built toolchain (crossdev -C armv6j-hardfloat-linux-gnueabi) and run this instead: CFLAGS="-O2 -pipe" CXXFLAGS="${CFLAGS} crossdev -S -v -t armv6j-hardfloat-linux-gnueabi From time to time, crossdev has trouble with -march options, so this will build it with minimal CFLAGS.
(In reply to comment #5) > Try removing the partially built toolchain (crossdev -C > armv6j-hardfloat-linux-gnueabi) and run this instead: > CFLAGS="-O2 -pipe" CXXFLAGS="${CFLAGS} crossdev -S -v -t > armv6j-hardfloat-linux-gnueabi > From time to time, crossdev has trouble with -march options, so this will > build it with minimal CFLAGS. Thanks Chris, Your solution works perfectly. Many thanks for your help.
No problem, glad I could help.
*** This bug has been marked as a duplicate of bug 448206 ***