Re: [Boost-build] Building / testing trunk broken for the Borlandtoolset.

From: Robert Ramey (ramey_at_[hidden])
Date: 2008-04-27 11:46:55

This is me.

In the past, I've made the building/testing of the serialization library
conditional on the installation of the spirit 1.6x library.  This
requires spirt 1.6 + an environmental variable setting indicating
the directory where it is to be found.

In V2 - I tried to update my Jamfile to handle this but have
been unsuccessful.  I did ask for help on this a couple of
times on the build list - but the response I got suggested
what I did should work - so here we are.

I would love to get this fixed so I could test this
compiler on my own system.

Another note - I now get warnings that some
headers I use from the spirit library are now
"deprecated".  If I were to "upgrade" the calls
to spirit to elminate these warnings, then the
xml serialization would not not work with
spirit 1.6x so that leaves me in a quandry.

On the other hand, the latest enhancments
to binary archives broke borland serialization
in a different way - so maybe we might as
we'll just forget about borland compatibility.

Robert Ramey

I've attempted to ma
John Maddock wrote:
> This is a strange one:
>
> if I cd into boost-root/status and do a:
>
> bjam msvc
>
> then everything is fine, but:
>
> bjam borland-5.8.2 fails with:
>
> **** spirit 1.6x required to build library with this compiler ****
> **** spirit 1.6x required to build library with this compiler ****
> Skipping build of:  ../libs/serialization/build/boost_wserialization
> <build>no in common properties
> c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:742:
> in actualize-source-type
> rule ../../config/test/all//BOOST_NO_STD_LOCALE.type unknown in module
> object(action)@12902.
> c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:764:
> in actualize-sources
> c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:709:
> in object(action)@12902.actualize
> c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:275:
> in actualize-action
> c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:462:
> in actualize-no-scanner
> c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:118:
> in object(file-target)@12903.actualize
> c:/data/boost/boost/trunk/tools/build/v2\build-system.jam:680: in load
> c:\data\boost\boost\trunk\tools\build\v2/kernel\modules.jam:267: in
> import
> c:\data\boost\boost\trunk\tools\build\v2/kernel/bootstrap.jam:134: in
> boost-build
> c:\data\boost\boost\trunk\boost-build.jam:11: in module scope
>
> This came to me because the the failure points to a Boost.Config
> Jamfile,
> but if I cd into that directory then it builds just fine with the
> borland
> toolset!
>
> I suspect this may be Boost.Serialization related given that that is
> the
> only library to reference libs/config/test/all/Jamfile.v2, but I'm
> completely stumped at this point.
>
> Any ideas anyone?
>
> Many thanks, John.
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build