Ernillew / wl500g

Automatically exported from code.google.com/p/wl500g
0 stars 0 forks source link

Use of uclibc-4.3.5-K26-x86_64-3 makes compilation problem on Debian Lenny #226

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Debian Lenny x64
2. new hndtools-mipsel-uclibc-4.3.5-K26-x86_64-3
3. build RTN version

# uname -a
Linux vector 2.6.26-2-amd64 #1 SMP Tue Jan 25 05:59:43 UTC 2011 x86_64 GNU/Linux

What is the expected output? What do you see instead?
I've expected compiled firmwares, but got that:

making selected firmwares...
grep: /home/asus/linux/linux-2.6/include/linux/utsrelease.h: No such file or 
directory
[ ! -d libbcmcrypto ] || make -C libbcmcrypto install 
INSTALLDIR=/home/asus/gateway/mipsel-uclibc/install/libbcmcrypto
find: `/home/asus/gateway/mipsel-uclibc/target': No such file or directory
make[1]: Entering directory `/home/asus/gateway/libbcmcrypto'
rm -rf /home/asus/gateway/mipsel-uclibc/install/libbcmcrypto
install -d /home/asus/gateway/mipsel-uclibc/install/libbcmcrypto/usr/lib
install -m 755 libbcmcrypto.so 
/home/asus/gateway/mipsel-uclibc/install/libbcmcrypto/usr/lib/libbcmcrypto.so
mipsel-uclibc-strip 
/home/asus/gateway/mipsel-uclibc/install/libbcmcrypto/usr/lib/libbcmcrypto.so
mipsel-uclibc-strip: /lib/libc.so.6: version `GLIBC_2.11' not found (required 
by mipsel-uclibc-strip)
make[1]: *** [install] Error 1

Please provide any additional information below.
use of hndtools-mipsel-uclibc-4.3.5-K26-x86_64-2 leads to the same problem.
Only use of hndtools-mipsel-uclibc-4.3.5-K26-2 leads to the full compilation 
process.

Original issue reported on code.google.com by vectorm...@gmail.com on 6 May 2011 at 6:15

GoogleCodeExporter commented 9 years ago
Debian Lenny x64 uses obsolete glibc 2.7 (according dpkg output provided by you 
in wl500g.info forum) while toolchain requires glibc 2.11 at least. 
Unfortunately, I haven't build environment with such old glibc.

So, the only two ways to solve problem:

1) rebuild toolchain by yourself

2) provide access for us for toolchain rebuild

Anyway, I will add comment about glibc version to download details.

Original comment by lly.dev on 6 May 2011 at 7:00