On 5/9/05, Dave Snowdon
Compiling boost 1.32 with gcc 3.3 (bjam "-sTOOLS=darwin" "-sGCC=gcc-3.3" "-sGXX=gcc-3.3" stage) gives some rather strange results. Link actions seems to fail such as:
...failed darwin-Link-DyLib-action bin/boost/libs/date_time/build/libboost_date_time.dylib/darwin/debug/shared-linkable-true/libboost_date_time-d-1_32.dylib...
Almost all the calls to ld gives undefined symbol errors similar to (I'm not sure if this is due to previously failed link actions):
darwin-Link-DyLib-action bin/boost/libs/date_time/build/libboost_date_time.dylib/darwin/debug/shared-linkable-true/libboost_date_time-d-1_32.dylib
ld: Undefined symbols:
__ZNKSbIwSt11char_traitsIwESaIwEE3endEv [...]
This looks like an error caused by linking with "gcc" instead of "g++". When you use gcc as your linker, it doesn't automatically pull in libstdc++, which might explain the unresolved externals. Perhaps you should try "-sGXX=g++-3.3" -- Caleb Epstein caleb dot epstein at gmail dot com