Re: [jamboost] gcc-stlport failing on Cygwin?

From: David Abrahams (dave_at_[hidden])
Date: 2003-01-24 10:03:58

"Raoul Gough" <raoulgough_at_[hidden]> writes:

> 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?

I have no idea; it's a longstanding mystery. Boost.Build isn't
supposed to work that way, and this is the only toolset which does
that to my knowledge.

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution