eglibc-2.17 build breaks with nptl #include nested too deeply
Has anyone seen this issue before - my builds are failing with the following:
from ../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23,
from ../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23,
from ../ports/sysdeps/arm/nptl/pthread_spin_lock.c:23:../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23:47: error: #include nested too deeply
Google only returns a recent discussion on the Cygwin list:
http://cygwin.1069669.n5.nabble.com/BUG-Ability-to-access-nonexistent-directories-td98708.html
But, I'm building this on Ubuntu 12.04, not Cygwin. Any pointers, while I keep digging? Thanks.
Signature · 1 line
Denys
Quoted 5 lines · Denys Dmytriyenko
Has anyone seen this issue before - my builds are failing with the following:
from ../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23, from ../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23, from ../ports/sysdeps/arm/nptl/pthread_spin_lock.c:23:
Quoted 8 lines
../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23:47: error: #include nested too deeplyGoogle only returns a recent discussion on the Cygwin list:
http://cygwin.1069669.n5.nabble.com/BUG-Ability-to-access-nonexistent-directories-td98708.html
But, I'm building this on Ubuntu 12.04, not Cygwin. Any pointers, while I keep digging? Thanks.
Well, a clean build seems to fix it... It's rather unfortunate that periodically incremental builds of the master break like that and can't recover on their own w/o cleaning up the temp directory.
Signature · 1 line
Denys