
On Thu, Jun 16, 2011 at 1:39 PM, Igor R
But how come that it seems not to be required to link against Boost.System when using boost-1.40 or boost-1.41 even though Boost.Filesystem is used and also included during linking? Has this requirement been introduced only recently? If so, it would be interesting to know since when exactly.
By the way, perhaps your toolset supports auto-link, so the boost.system in the "global installation" was just automatically linked?
Just take a look at previosly produced binaries, if the Boost.System symbol(s) is(are) there... smth. like: nm binary_name | grep some_expected_symbol_name_from_boost_system Than you will definitely know if Boost.System (somehow) linked with produced executable as well. With Kind Regards, Ovanes