Hi Waldemar,
I started to play more with uClibc-ng and in particular tried to integrate it in OpenWRT build system. And even thought I got all built from the first attempt on boot kernel reported init failure.
Basically it was because missing ld-uClibc.so.0 against which all dynamically linked apps were built.
I noticed in Buildroot we cure that manually this way http://git.buildroot.net/buildroot/commit/package/uclibc/uclibc.mk?id=1deb42...
But problem with that approach is each and every build system/script will need to care about creation of those links, which is a bit inconvenient. People don't expect that kind of a problem so it will make witch from vanilla uClibc to uClibc-ng not completely painless.
So I'm wondering if in uClibc-ng itself we may have creation of corresponding links and later installation of them on target?
-Alexey
Hi Alexey, Alexey Brodkin wrote,
Hi Waldemar,
I started to play more with uClibc-ng and in particular tried to integrate it in OpenWRT build system. And even thought I got all built from the first attempt on boot kernel reported init failure.
Basically it was because missing ld-uClibc.so.0 against which all dynamically linked apps were built.
I noticed in Buildroot we cure that manually this way http://git.buildroot.net/buildroot/commit/package/uclibc/uclibc.mk?id=1deb42...
But problem with that approach is each and every build system/script will need to care about creation of those links, which is a bit inconvenient. People don't expect that kind of a problem so it will make witch from vanilla uClibc to uClibc-ng not completely painless.
So I'm wondering if in uClibc-ng itself we may have creation of corresponding links and later installation of them on target?
Yes, this is something we need to do. Thanks for requesting it. I hopefully integrated a useful patch to git.
http://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=9b9abfbd25d5f950...
best regards Waldemar
-
Alexey Brodkin -
Waldemar Brodkorb