[uclibc-ng] Fail to build [libc/inet/if_index.os] when building uClibc-ng 1.0.12 with 2.6.22.19 kernel headers
Hi,
I need to build a mipsel toolchain with pretty old kernel headers (2.6.22.19: http://wl500g.googlecode.com/files/linux-2.6.22.19.tar.bz2). This leads to an error, very similar to the one described here: https://bugs.busybox.net/show_bug.cgi?id=6278 (see exact output in error.log attached). I think this is a kernel bug, but I do need a 2.6.22 toolchain for better mipsel routers support (many of them, like Asus ones, run 2.6.22.19 kernels, and using a toolchain with newer kernel headers has proved to cause numerous issues). Is there a possible workaround for this issue?
Thanks, Alex Potapenko
Hi Alex, Alex Potapenko wrote,
Hi,
I need to build a mipsel toolchain with pretty old kernel headers (2.6.22.19: http://wl500g.googlecode.com/files/linux-2.6.22.19.tar.bz2). This leads to an error, very similar to the one described here: https://bugs.busybox.net/show_bug.cgi?id=6278 (see exact output in error.log attached). I think this is a kernel bug, but I do need a 2.6.22 toolchain for better mipsel routers support (many of them, like Asus ones, run 2.6.22.19 kernels, and using a toolchain with newer kernel headers has proved to cause numerous issues). Is there a possible workaround for this issue?
I rather would like to avoid supporting such very old kernels. The oldest supported kernel is 2.6.32.70. Could you try using this for the toolchain? What runtime problems occur, when you use 2.6.32.70 for toolchain and then run the code on 2.6.22.19?
I verified that 2.6.32.70 works with uClibc-ng for mipsel toolchain.
best regards Waldemar
Hi Waldemar,
2016-02-09 21:46 GMT+02:00 Waldemar Brodkorb wbx@uclibc-ng.org:
I rather would like to avoid supporting such very old kernels. The oldest supported kernel is 2.6.32.70. Could you try using this for the toolchain? What runtime problems occur, when you use 2.6.32.70 for toolchain and then run the code on 2.6.22.19?
I verified that 2.6.32.70 works with uClibc-ng for mipsel toolchain.
I haven't tried 2.6.32.70 -- the issues I had happened with 2.6.36.4 toolchain on 2.6.22.19 system. One issue I'm absolutely sure is due to older kernel is this one: https://sourceware.org/ml/gdb-prs/2015-q4/msg00337.html I later found out that ARMv5 gdb has the same issue if run on 2.6.12, but works OK on my test 2.6.36.4 machine (2.6.36.4 toolchain as well). And there're others that are very hard to debug, e.g., I found out that php crashes when configuring owncloud8 if pdo_mysql module is loaded (this doesn't happen on other test targets where systems run kernels not older than toolchains').
I also see that Entware-ng project is using 2.6.22.19 kernel with uClibc-ng 1.0.9. They're also using quite a lot of uClibc-ng patches: https://github.com/Entware-ng/Entware-ng/tree/master/toolchain/uClibc/patche... The first two are safe to ignore (they're just hardcoding '/opt' into prefix definitions, I don't need that -- I configure UCLIBC_RUNTIME_PREFIX as '/opt' instead; well, I'd need some parts of the patches to get working utils on the target system, but I don't package them as of now), but I wonder if some of the others would make uClibc-ng compile with 2.6.22.19 headers? It'd be good if you could take a look.
Thanks, Alex
P.S. I'll try 2.6.32.70 headers as soon as I can
Hi Alex, Alex Potapenko wrote,
Hi Waldemar,
2016-02-09 21:46 GMT+02:00 Waldemar Brodkorb wbx@uclibc-ng.org:
I rather would like to avoid supporting such very old kernels. The oldest supported kernel is 2.6.32.70. Could you try using this for the toolchain? What runtime problems occur, when you use 2.6.32.70 for toolchain and then run the code on 2.6.22.19?
I verified that 2.6.32.70 works with uClibc-ng for mipsel toolchain.
I haven't tried 2.6.32.70 -- the issues I had happened with 2.6.36.4 toolchain on 2.6.22.19 system. One issue I'm absolutely sure is due to older kernel is this one: https://sourceware.org/ml/gdb-prs/2015-q4/msg00337.html I later found out that ARMv5 gdb has the same issue if run on 2.6.12, but works OK on my test 2.6.36.4 machine (2.6.36.4 toolchain as well). And there're others that are very hard to debug, e.g., I found out that php crashes when configuring owncloud8 if pdo_mysql module is loaded (this doesn't happen on other test targets where systems run kernels not older than toolchains').
I also see that Entware-ng project is using 2.6.22.19 kernel with uClibc-ng 1.0.9. They're also using quite a lot of uClibc-ng patches: https://github.com/Entware-ng/Entware-ng/tree/master/toolchain/uClibc/patche... The first two are safe to ignore (they're just hardcoding '/opt' into prefix definitions, I don't need that -- I configure UCLIBC_RUNTIME_PREFIX as '/opt' instead; well, I'd need some parts of the patches to get working utils on the target system, but I don't package them as of now), but I wonder if some of the others would make uClibc-ng compile with 2.6.22.19 headers? It'd be good if you could take a look.
Most of the patches in Entware-ng are already in uClibc-ng 1.0.12. I see no related patch to your issues.
Can you please update your uClibc-ng to 1.0.12?
P.S. I'll try 2.6.32.70 headers as soon as I can
Thx.
I will check the gdb issue on my MIPSel system. If your php crashed with some dso, I have this for you: https://lists.uclibc.org/pipermail/uclibc/2013-November/048061.html
best regards Waldemar
Hi Waldemar,
2016-02-10 21:28 GMT+02:00 Waldemar Brodkorb wbx@uclibc-ng.org:
I will check the gdb issue on my MIPSel system. If your php crashed with some dso, I have this for you: https://lists.uclibc.org/pipermail/uclibc/2013-November/048061.html
Thanks. That thread holds no answer, right? Also, `php -m` doesn't segfault in my case, but php-cgi crashes when configuring owncloud-8 if pdo-mysql dso is loaded.
P.S. I'll try 2.6.32.70 headers as soon as I can
Thx.
Sorry, I haven't tried 2.6.32.70 as promised --- instead I looked into Entware-ng code and found out that they're using this custom 2.6.22.19 mipsel kernel: https://github.com/wl500g/wl500g/tree/master/linux/linux-2.6.22.19 I verified that uclibc-ng 1.0.12 builds with these headers fine. I'm now proceeding further with the toolchain and on with building the feed. I'll also try gdb on the target system to check whether the issue was indeed due to newer kernel headers or not.
Thanks, Alex
2016-02-11 17:57 GMT+02:00 Alex Potapenko opotapenko@gmail.com:
I'll also try gdb on the target system to check whether the issue was indeed due to newer kernel headers or not.
Bingo! Confirmed, it works fine with 2.6.22.19 kernel toolchain with uClibc-ng 1.0.12.
Best regards, Alex
-
Alex Potapenko -
Waldemar Brodkorb