boost serialization linking problems with certain binutils
hi, im looking for feedback as well as a possible fix for boost serialization with binutils >2.15.90.0.* with binutils 2.15.90.0.* the boost serialization demo links properly with newer (stable on gentoo) binutils we see a myriad of gnu linkonce errors from the linker so i would like to know if anyone here can link the serialization demo.cpp with 2.15.92.* binutils if yes on which distro and the exact version of the binutils better yet, i would like to know how i can build boost serialization also as a shared lib, as none of the other libs which exist in shared and static version have problems with linking with 2.15.92.* bintuils thank you in advance for your input and help Daniel
Daniel Goller wrote:
hi,
im looking for feedback as well as a possible fix for boost serialization with binutils >2.15.90.0.* with binutils 2.15.90.0.* the boost serialization demo links properly with newer (stable on gentoo) binutils we see a myriad of gnu linkonce errors from the linker
so i would like to know if anyone here can link the serialization demo.cpp with 2.15.92.* binutils if yes on which distro and the exact version of the binutils
Note that our test matrix shows most tests passing compile, link and run tests. http://www.meta-comm.com/engineering/boost-regression/developer/serializatio n.html These tests are on current state of the next version to be released. In order to function with gcc 2.95 we use STLPort 4.5.3 rather than the standard library that comes with gcc 2.95 as well as spirit 1.6x rather than the curent spirit 1.8x
better yet, i would like to know how i can build boost serialization also as a shared lib,
Note the current test version permits bulding of the serialization library as a shared lib. I don't know the next version of boost (1.33) will be released. As a practical matter to use gcc 2.95 with the serialization library you will have to change standard library to STLPort and use sprite 1.6x. Given this, it might just be easier to upgrade your gcc to 3.4x which is much better in any case. Robert Ramey
Robert Ramey wrote:
Daniel Goller wrote:
hi,
im looking for feedback as well as a possible fix for boost serialization with binutils >2.15.90.0.* with binutils 2.15.90.0.* the boost serialization demo links properly with newer (stable on gentoo) binutils we see a myriad of gnu linkonce errors from the linker
so i would like to know if anyone here can link the serialization demo.cpp with 2.15.92.* binutils if yes on which distro and the exact
version of the binutils
Note that our test matrix shows most tests passing compile, link and run tests.
http://www.meta-comm.com/engineering/boost-regression/developer/serializatio n.html
checking link now
These tests are on current state of the next version to be released. In order to function with gcc 2.95 we use STLPort 4.5.3 rather than the standard library that comes with gcc 2.95 as well as spirit 1.6x rather than the curent spirit 1.8x
better yet, i would like to know how i can build boost serialization also as a shared lib,
i would need a better understanding of how bjam files work to port this im afraid
Note the current test version permits bulding of the serialization library as a shared lib.
I don't know the next version of boost (1.33) will be released.
As a practical matter to use gcc 2.95 with the serialization library you will have to change standard library to STLPort and use sprite 1.6x. Given this, it might just be easier to upgrade your gcc to 3.4x which is much better in any case.
appologies for not mentioning this is with gcc 3.3.x and gcc 3.4.x (gcc-3.4.3 being personal preference, gcc-3.3.5 being gentoo default)
Robert Ramey
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
a
Whoops, for some reason I presumed this was a problem with an older gcc. Anyway, I build here with gcc under cygwin. No problems (except wide char i/o not supported w/o stlport). This is the first I've heard of any such problem, so maybe is specific to something in your installation. Sorry I can say what it might be. Robert Ramey
Robert Ramey wrote:
Whoops, for some reason I presumed this was a problem with an older gcc.
my fault for omitting the info by accident
Anyway, I build here with gcc under cygwin. No problems (except wide char i/o not supported w/o stlport).
i can build it all fine, i will just have to stick to 2.15.90.0.3 of binutils till i have a real solution
This is the first I've heard of any such problem, so maybe is specific to something in your installation. Sorry I can say what it might be.
which is why i was hoping to get feedback from people with other distros might just have to run a debian chroot/colinux sometime thanks for your info, ill be looking into porting the serialization change to 1.32.0 if the binutils issue can not be resolved
Robert Ramey
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (2)
-
Daniel Goller -
Robert Ramey