Bryce Lelbach
Could anyone who's been having a problem with Serialization archive back compatibility please update from the SVN trunk and check if the problem still exists? It should be fixed as of r66107.
Sorry to say that, but no, svn trunk does NOT fix the static linking problem. I compiled the svn trunk r66115 with the following command: bjam.exe -q --layout=system --with-system --with-thread --with-python --with-serialization toolset=gcc variant=release link=static threading=multi runtime-link=static Compilation takes bloody ages and produces a lot of this warning:
warning: visibility attribute not supported in this configuration; ignored
After that, trying to link an application using portable_binary_oarchive with libboost_serialization.a results in the following linker erros: Cannot export _ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_iarchiveEEE12get_instanceEv: symbol not found Cannot export _ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_iarchiveEEE12is_destroyedEv: symbol not found Cannot export _ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_iarchiveEEE18get_const_instanceEv: symbol not found Cannot export _ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_iarchiveEEE20get_mutable_instanceEv: symbol not found Cannot export _ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_oarchiveEEE12get_instanceEv: symbol not found Cannot export _ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_oarchiveEEE12is_destroyedEv: symbol not found Cannot export _ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_oarchiveEEE18get_const_instanceEv: symbol not found Cannot export ZN5boost13serialization9singletonINS_7archive6detail12_GLOBAL__N_13mapI24 portable_binary_oarchiveEEE20get_mutable_instanceEv: symbol not found Regards, Philipp