[Boost-build] Change of target's path from relative to absolute

Subject: [Boost-build] Change of target's path from relative to absolute
From: John Bito (jwbito_at_[hidden])
Date: 2009-08-11 20:43:38

I just deployed the HEAD of Boost.Build (at 55533) and my integration
build server got a failure, seemingly because a command line exceeded
some limit.  It appears that the build now is passing full path names
to the actions where it formerly passed relative names.  Does that
sound like a consequence of a change in Boost.Build?  Maybe because
the module with the target rule is imported at the root of the build??
 Still trying to track this down.