[uClibc]Trouble with uclibc toolchain and mipsel

Dana Soward dana at linuxboxen.org
Tue Dec 10 02:08:35 UTC 2002


I posted this a week or so ago, but never got a response (I also noticed
I sent it in RTF, sorry about that...) so I'm posting again...I DID try
gcc 3.2, and it did compile properly, however, when I try to use it to
compile anything, even busybox, I get "Bus Error"s and "Illegal
Instruction" errors randomly.  And by randomly I mean it never happened
on the same part of the build, or in any specific package (I tried
busybox, openssl, and openssh).  Oh, also, the gcc 2.95 configure script
cant seem to detect my host system...I did tell it manually, but I
thought it odd that it had trouble when binutils found it just fine....

I get the following error when attempting to build the 0.9.15
toolchain...

make -C  internals
make[4]: Entering directory
`/root/gcc-2.95/build/uClibc-0.9.15/libc/misc/internals'
/usr/local/uclibc/bin/mipsel-uclibc-gcc -Wall -Wall -Wstrict-prototypes
-Wno-trigraphs -fno-strict-aliasing -Os -fno-builti
n -nostdinc  -I../../../include -iwithprefix include -I. -D_LIBC
-DNDEBUG  -fPIC -c tempname.c -o tempname.o
tempname.c: In function `__gen_tempname':
tempname.c:218: Internal compiler error in `find_reloads', at
reload.c:2584
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[4]: *** [tempname.o] Error 1
make[4]: Leaving directory
`/root/gcc-2.95/build/uClibc-0.9.15/libc/misc/internals'
make[3]: *** [_dir_internals] Error 2
make[3]: Leaving directory
`/root/gcc-2.95/build/uClibc-0.9.15/libc/misc'
make[2]: *** [_dir_misc] Error 2
make[2]: Leaving directory `/root/gcc-2.95/build/uClibc-0.9.15/libc'
make[1]: *** [_dir_libc] Error 2
make[1]: Leaving directory `/root/gcc-2.95/build/uClibc-0.9.15'
make: *** [/root/gcc-2.95/build/uClibc-0.9.15/lib/libc.a] Error 2

I found the same problem in a previous email to the list
(http://www.uclibc.org/lists/uclibc/2002-July/006171.html) and it was
suggested that the host gcc (2.96) was to blame.  I'm actually using gcc
2.95.3 for mipsel, and my host system is also my target system.  Do I
need to try and build gcc 3.x for this? I don't know much about how this
build works, but it looks like the target gcc I just built
(/usr/local/uclibc/bin/mipsel-uclibc-gcc) is the one having problems. Is
that an actual gcc? Or just a wrapper? Should I try gcc 3.2 as the
target gcc? Or is that not the issue?  Any help would be great..if you
need more info about the host system let me know.(im not sure whats
useful.

Thanks

Dana Soward
Email: dana at linuxboxen.org




More information about the uClibc mailing list