[pkg-boost-devel] Bug#433342: libboost-serialization1.33.1 is missing

Domenico Andreoli cavokz at gmail.com
Mon Jul 16 22:14:44 UTC 2007


[ please keep CCing to 433342 at bugs.debian.org ]

On Mon, Jul 16, 2007 at 11:29:32PM +0200, Carlo Wood wrote:
> On Mon, Jul 16, 2007 at 05:58:16PM +0200, Domenico Andreoli wrote:
> > Hi Carlo,
> > 
> >   unfortunately when I was pointed Boost.Serialization had also a shared
> > library (initially it had not) it was too late for it to be included
> > in Etch. So the library is really missing and can not be added. Sorry.
> 
> I don't have etch, I have lenny (testing). You can still add it
> to testing, can't you?

ah.. ok :)

boost 1.33.1 in testing will be replaced by 1.34.0 (most probably by
1.34.1) which is in unstable, it already has Boost.Serialization as
libboost-serialization1.34.0.

> It is very unclear how to link with boost libraries anyway.

this is what is keeping boost 1.34.x out of testing. those long names
(ie. libboost_program_options-gcc-mt-1_33_1.so) are the "regular" ones,
those that come out of the build as upstream made it. it is explained
in the Boost documentation [0].

shorter names (ie. libboost_program_options.so) are commodity but
unportable names which have been introduced some time ago. the full story
is available in bug repoorts #429533, #424038, #424666, #425992, #428419.

> So, what about the other four?
> 
> /usr/lib/libboost_program_options-gcc-1_33_1.a
> /usr/lib/libboost_program_options-gcc-1_33_1.so.1.33.1
> /usr/lib/libboost_program_options-gcc-d-1_33_1.so.1.33.1
> /usr/lib/libboost_program_options-gcc-mt-d-1_33_1.so.1.33.1
> 
> Those are the libraries that either do not have -mt or do have -d in them.
> 
> Linking with libboost_program_options-gcc-1_33_1.a could be done
> by using -lboost_program_options-gcc-1_33_1 but linking
> with the other three can't even be done without changing the
> default symlink. 

those ending with .so.1.33.1 are the real libraries, you should not
link directly to them.

> Is there some tool that I am not aware of that I should be using
> (as developer) to get my applications to link to some version
> of a boost library of my choice?

unfortunately not, the only portable way to link to any boost library
is building its name [0]. 

cheers
domenico

[0] http://www.boost.org/more/getting_started/unix-variants.html#library-naming

-----[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50




More information about the pkg-boost-devel mailing list