Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3125 - uclibc++ doesn't build when generated file names are too long #7878

Open
openwrt-bot opened this issue May 26, 2020 · 1 comment
Open
Labels

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented May 26, 2020

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:

  1. Configure to build image for Turris Omnia.
  2. Build with: 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.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented May 26, 2020

wt:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant