OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version Trunk
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Wren Turkal - 26.05.2020

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

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:

If this patch get’s accepted upstream, we should add a patch to package/libs/uclibc++/patches/ for this.


Wren Turkal commented on 26.05.2020 05:19

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.


Available keyboard shortcuts


Task Details

Task Editing