headers
K.Noel Belcourt | 18 Nov 20:44
Favicon

darwin DYLD_LIBRARY_PATHn environment variable problem

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.

-- Noel

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
(Continue reading)

Permalink | Reply |
headers
Vladimir Prus | 18 Nov 20:56
Favicon

Re: darwin DYLD_LIBRARY_PATHn environment variable problem

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.
(Continue reading)

Permalink | Reply |
headers
Steven Watanabe | 18 Nov 20:59

Re: darwin DYLD_LIBRARY_PATHn environment variable problem

AMDG

K.Noel Belcourt wrote:
> 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.

Are you using a bjam from before
(Continue reading)

Permalink | Reply |
headers
K. Noel Belcourt | 18 Nov 20:56
Favicon

Re: darwin DYLD_LIBRARY_PATHn environment variable problem

Please ignore, I had updated from the trunk but failed to rebuild the  
bjam binary.

-- Noel

On Nov 18, 2008, at 12:44 PM, 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
(Continue reading)

Permalink | Reply |

Gmane