Hi guys: I've managed to patch uclibc so it compiles (.c -> .o) but it is failing at the linking stage. The problem seems to be a big-endian / little-endian prob, but I can't find a solution.
I don't understand why the cross-toolchain is worrying about endianness... Aren't these tools meant to run on my x86 host to produce target binaries?!? Shouldn't they have x86-endiannes? Any help/guidance highly appreciated! Arturo. btw, my command line is: UCLIBC_CPU='ARM_XSCALE' crossdev --k 2.6.21 --l 0.9.28.3 --target armeb-softfloat-linux-uclibc Is that wrong? Should I be using GENERIC_ARM? Thanks! *** ERROR BELOW *** armeb-softfloat-linux-uclibc-ld: /usr/lib/gcc/armeb-softfloat-linux-uclibc/4.1.2/libgcc.a(_udivsi3.o): compiled for a big endian system and target is little endian ... ... ... lots of stuff that says the same ... ... ... armeb-softfloat-linux-uclibc-ld: BFD 2.17 assertion fail /var/tmp/cross/armeb-softfloat-linux-uclibc/portage/cross-armeb-softfloat-linux-uclibc/binutils-2.17-r1/work/binutils-2.17/bfd/elf32-arm.c:3740 armeb-softfloat-linux-uclibc-ld: BFD 2.17 assertion fail /var/tmp/cross/armeb-softfloat-linux-uclibc/portage/cross-armeb-softfloat-linux-uclibc/binutils-2.17-r1/work/binutils-2.17/bfd/elf32-arm.c:3740 make[1]: *** [shared] Error 1 make[1]: Leaving directory `/var/tmp/cross/armeb-softfloat-linux-uclibc/portage/cross-armeb-softfloat-linux-uclibc/uclibc-0.9.28.3/work/uClibc-0.9.28.3/libc' make: *** [shared] Error 2 -- [EMAIL PROTECTED] mailing list
