I am working on building a project that relies on OpenSG2 and VR Juggler 2.2 for various reasons between the two I am building Boost 1_37 for the boost co dependency. While working with VR Juggler I noticed the error that boost::filesystem::exists was not defined in libboost_filesystem-xgcc40-mt.dylib. Which I found a little odd. After looking in to it I noticed that it is indeed not defined in either on of my release libs, but was defined in all of the debug libraries. In case I had done something wrong when I compiled boost I started a recompile with the following options. bjam --tool-set=darwin --prefix=$HOME/usr -- build-type=complete -a stage It currently looks like the build will yield the same results. I have a few nm | grep | c++filt below for the new libs. So I have two questions. Is the behavior below normal. If not what might be the cause? nm bin.v2/libs/filesystem/build/darwin-4.0.1/release/link-static/runtime-link-static/threading-multi/libboost_filesystem-xgcc40-mt-s-1_37.a | grep exists | c++filt 000003b0 T boost::filesystem::detail::symbolic_link_exists_api(std::basic_string const&) 0002cc00 S __ZN5boost10filesystem6detail24symbolic_link_exists_apiERKSs.eh nm bin.v2/libs/filesystem/build/darwin-4.0.1/debug/link-static/runtime-link-static/threading-multi/libboost_filesystem-xgcc40-mt-sd-1_37.a | grep exists | c++filt 000005a4 T boost::filesystem::detail::symbolic_link_exists_api(std::basic_string const&) 00025cf4 S __ZN5boost10filesystem6detail24symbolic_link_exists_apiERKSs.eh 00021fe8 S boost::files nm stage/lib/libboost_filesystem-xgcc40-mt-d-1_37.dylib |grep exists | c++filt 00002822 T boost::filesystem::detail::symbolic_link_exists_api(std::basic_string const&) 00004872 T boost::filesystem::exists(boost::filesystem::file_status) volcano boost_1_37_0]$ nm stage/lib/libboost_filesystem-xgcc40-mt-1_37.dylib | grep exists | c++filt 00002010 T boost::filesystem::detail::symbolic_link_exists_api(std::basic_string const&)