ok, finally trying out the uclibc patch for crosstool...

[Dan Kegel]

Dan Kegel wrote:
>> Did crosstool get fired up with TARGET=mipsel-unknown-linux-gnu but with
>> LIBC_DIR=uClibc-0.9.23?
>>
>> The linux-gnu TARGET suffix asks gcc and binutils to build assuming 
>> glibc.
>> I don't know what to expect (aside from general badness) if you configure
>> for glibc but build with uClibc.
>>
>> Try changing the TARGET line in mipsel.dat to:
>>
>> TARGET=mipsel-unknown-linux-uclibc
> 
> Trying it now.

That worked much better.  It actually built a toolchain!
However, the toolchain failed the "hello, c++" test for
dynamically linked executables (though static was ok).
Here's the last couple lines of the log:

+ /opt/crosstool/mipsel-unknown-linux-uclibc/gcc-3.3.3-uClibc-0.9.23/bin/mipsel-unknown-linux-uclibc-g++ -static hello2.cc -o mipsel-unknown-linux-uclibc-hello2-static
+ /opt/crosstool/mipsel-unknown-linux-uclibc/gcc-3.3.3-uClibc-0.9.23/bin/mipsel-unknown-linux-uclibc-g++ hello2.cc -o mipsel-unknown-linux-uclibc-hello2
/opt/crosstool/mipsel-unknown-linux-uclibc/gcc-3.3.3-uClibc-0.9.23/lib/gcc-lib/mipsel-unknown-linux-uclibc/3.3.3/../../../../mipsel-unknown-linux-uclibc/lib/libstdc++.so: undefined reference to `sqrtf'
collect2: ld returned 1 exit status

which looks a bit similar to http://gcc.gnu.org/PR8197

Perhaps dstrohschein@thewifilink.com can try out this toolchain
and report whether it worked for him at all with -static...
- 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