Reply With Quotethe reason is an old uclibc.
use something like this:
CC=mipsel-uclibc-gcc ./configure --host=mipsel-linux bla-bla-bla
Member
The autoconf scripts doesn't like the names of the executables in our toolchain. If you pass --host=mipsel-uclibc to the configure script, it says that uclibc system is unknown. If you pass mipsel-linux, it uses the wrong tool chain (glibc based).
Using mipsel-uclibc-linux, the script doesn't found gcc, ld, strip, ... So I've renamed all the binaries using "mipsel-uclibc-linux-" as prefix instead of "mipsel-uclibc-". This way, all is compiled correctly.
Oleg, is there a reason to name the executables the way is currently done?
Administrator
the reason is an old uclibc.
use something like this:
CC=mipsel-uclibc-gcc ./configure --host=mipsel-linux bla-bla-bla
Posting Permissions