First, because during linking, the linker included with 10.4 doesn't make use of the -L path for finding indirectly referenced dylibs like libboost_system-1_35.dylib is in the example I gave... requiring the use of the -dylib_file option, something pretty non-standard. Second, because at run time, this requires setting the DYLIB_PATH, which is discouraged by apple. Sancho On Fri, May 2, 2008 at 10:00 AM, Rene Rivera wrote:

Sancho McCann wrote:

...

This seems to be a problem for a few of the dynamic libraries.

Running otool on libboost_filesystem, for example, gives:

otool -L /opt/local/lib/libboost_filesystem-mt-1_35.dylib /opt/local/lib/libboost_filesystem-mt-1_35.dylib: /opt/local/lib/libboost_filesystem-mt-1_35.dylib (compatibility version 0.0.0, current version 0.0.0) libboost_system-mt-1_35.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.3)

The install_name of libboost_system-mt-1_35.dylib is missing the absolute path. How should this be addressed?

Why is it a problem?

-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users