$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: David Abrahams (dave_at_[hidden])
Date: 2005-06-08 11:35:04
"ANDREW MARLOW, BLOOMBERG/ LONDON OF" <amarlow1_at_[hidden]> writes:
> When bjam uses the archive command, it assumes that
> the length of the command line will be ok.
No it doesn't. There's extensive machinery in the bjam executable for
dealing with command-line length limitations.
> DOS has a ridiculously small limit, cygwin has
> a slightly larger limit and Unix has a much
> larger limit. But they all have limits.
> My jam is failing due to the limit and the
> large number of lengthy filenames I have.
>
> Shouldn't jam use a pipeline for the ar command
> in Unix-like environments? This avoids the
> command line length limit ever being a problem.
It does use such a pipeline, or at least it once did. It's possible
that some toolset author has disabled it. Hmm, it's still there in
BBv1, but apparently that functionality was not preserved in BBv2.
-- Dave Abrahams Boost Consulting www.boost-consulting.com