You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was having trouble building uClibc++ in Openwrt. I figured out that the problem was that the LIBSUP_DEP variable, which is a filename that gets created during the build, was too long for my file system. The name generated was over 150 char long and my fs has a limit of 143. I guess this because I have an encrypted homedir. Anyway, I analyzed the build system of uClibc++, and it seems to vary with the file location for libsupc++.a which is used to extract a bunch of symbols and create the static lib.
I had configured my build to build for a Turris Omnia.
Software versions: master branch of OpenWrt
Steps to reproduce:
Configure to build image for Turris Omnia.
Build with: make package/libs/uclibc++/compile -j1 V=sc
This task should probably be somewhat higher priority because I am building on a system with an encrypted home volume, which isn't that uncommon. My max file length is much shorter than the filename generated by the uclibc++ build.
wt:
I was having trouble building uClibc++ in Openwrt. I figured out that the problem was that the LIBSUP_DEP variable, which is a filename that gets created during the build, was too long for my file system. The name generated was over 150 char long and my fs has a limit of 143. I guess this because I have an encrypted homedir. Anyway, I analyzed the build system of uClibc++, and it seems to vary with the file location for libsupc++.a which is used to extract a bunch of symbols and create the static lib.
I had configured my build to build for a Turris Omnia.
Software versions: master branch of OpenWrt
Steps to reproduce:
make package/libs/uclibc++/compile -j1 V=sc
My proposed fix: https://bugs.busybox.net/show_bug.cgi?id=12951
If this patch get's accepted upstream, we should add a patch to package/libs/uclibc++/patches/ for this.
The text was updated successfully, but these errors were encountered: