Frank J. R. Hanstick wrote:
> /bin/sh ../libtool --tag=CXX --mode=link g++ -D_THREAD_SAFE -g -O2
> -lboost_system-xgcc40-mt-1_37.dylib -o browser browser.o
> libtest-openvrml.la -lboost_unit_test_framework-xgcc40-mt-1_37
> -lboost_filesystem-xgcc40-mt-1_37
> /usr/bin/ld: can't locate file for: -lboost_system-xgcc40-mt-1_37.dylib
Shouldn't this be -lboost_system-xgcc40-mt-1_37 (no .dylib)
Also, why is it in a different place from the other libs?
In Christ,
Steven Watanabe
>> /usr/bin/ld: can't locate file for: -lboost_system-xgcc40-mt-1_37.dylib
>Shouldn't this be -lboost_system-xgcc40-mt-1_37 (no .dylib)
There is not an -lboost_system-xgcc40-mt-1_37 input to g++ when this occurs, so, it had to be gotten from somewhere else, either internal to g++ which is unlikely or from libboost_filesystem_xgcc40-mt-1_37.
>Also, why is it in a different place from the other libs?
All Boost libraries are in /usr/local/lib where they are suppose to be. This is verified by the command:
make check LDFLAGS='-lboost_system-xgcc40-mt-1_37'
successfully finding libboost_system-xgcc-mt-1_37.dylib.
Come think of it, there is also a libboost_xxx-xgcc40-mt set of Boost libraries from an earlier install that gave the exact same error message when libboost_system_xgcc40-mt is not specified which would indicate that somewhere within libboost_filesystem_xgcc40-mt and libboost_filesystem_xgcc40-mt-1_37 is an improper link direction generated by the Boost library build that is overridden by the LDFLAGS input.