|
Boost-Build : |
From: Raoul Gough (raoulgough_at_[hidden])
Date: 2003-01-24 09:49:36
I'm trying to build with the gcc-stlport toolset on Cygwin, but I'm
getting "File or path name too long" errors from the assembler. The
problem is with the name of the object files, for example:
libs\regex\build\bin\libboost_regex.lib\gcc-stlport\debug\optimization
-off\runtime-link-dynamic\stlport-anachronisms-on\stlport-cstd-namespa
ce-std\stlport-debug-alloc-off\stlport-iostream-on\stlport-version-4.5
.3\c_regex_traits_common.obj
that's 238 characters, which would blow the MAX_PATH limit once the
PWD is added. I'm pretty sure there is a known limitation in the
Cygwin run time library (see
http://www.cygwin.com/ml/cygwin/2002-03/msg00256.html) that explains
this problem.
The error occurs whether or not I include
-sBUILD="<stlport-iostream>on"
on the jam command line. Has anyone managed to build with this toolset
on Cygwin recently? Why the complete feature-list in the object path
names?
Regards,
Raoul Gough.
--------- trace follows ---------
g++ -c -Wall -ftemplate-depth-100 -DBOOST_REGEX_NO_LIB=1 -DBOOST_REG
EX_STATIC_LINK=1 -D_STLP_DEBUG=1 -D_STLP_DEBUG_UNINITIALIZED=1 -D_STLP
_USE_DYNAMIC_LIB=1 -g -O0 -finline-functions -Wno-inline -I"libs\re
gex\build" -I "d:\boost\CVS\boost" -I
"d:/stlport/STLport-4.5.3\stlport" -o
"libs\regex\build\bin\libboost_regex.lib\gcc-stlport\debug\optimizatio
n-off\runtime-link-dynamic\stlport-anachronisms-on\stlport-cstd-namesp
ace-std\stlport-debug-alloc-off\stlport-iostream-on\stlport-version-4.
5.3\c_regex_traits_common.obj"
"libs\regex\build\../src\c_regex_traits_common.cpp"
Assembler messages:
FATAL: can't create
libs\regex\build\bin\libboost_regex.lib\gcc-stlport\debug\optimization
-off\runtime-link-dynamic\stlport-anachronisms-on\stlport-cstd-namespa
ce-std\stlport-debug-alloc-off\stlport-iostream-on\stlport-version-4.5
.3\c_regex_traits_common.obj: File or path name too long
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk