Re: [Boost-build] darwin DYLD_LIBRARY_PATHn environment variable problem

Subject: Re: [Boost-build] darwin DYLD_LIBRARY_PATHn environment variable problem
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2008-11-18 14:56:59

K.Noel Belcourt wrote:

> Hi,
> 
> It seems that a recent change to the build system resulted in
> failures of this sort, when running tests on OSX (either darwin or
> intel-darwin).
> 
> testing.capture-output ../bin.v2/libs/mesh/test/test_hfds.test/
> darwin-4.0.1/debug/test_hfds.run
> 
>      DYLD_LIBRARY_PATH=/Users/kbelco/boost/bin.v2/libs/mesh/build/
> darwin-4.0.1/debug:$DYLD_LIBRARY_PATHnexport DYLD_LIBRARY_PATHn
> 
> ...
> 
> /bin/sh: line 2: DYLD_LIBRARY_PATHn: command not found
> ====== BEGIN OUTPUT ======
> dyld: Library not loaded: libboost_mesh-xgcc40-d-1_38.dylib
>    Referenced from: /Users/kbelco/boost/status/../bin.v2/libs/mesh/
> test/test_hfds.test/darwin-4.0.1/debug/test_hfds
>    Reason: image not found
> 
> There is an extra 'n' showing up in the environment variable name.
> Anyone know where this is coming from?  It rather looks like an end
> of line character that is mis-interpreted on the Mac.

Yes, as I've said on boost-testing, the fact that outdated Boost.Jam is
used with SVN HEAD of Boost.Build is causing this problem. I'll poke Rene
again.

- Volodya