Re: vegastrike and libboost-python-dev
So, could we check in build time if it's libboost_python-st.so or
libboost_python.so that exists and use the correct one depending on
that? That's what usually the autotools stuff does.
Greetings,
Miry
2007/6/5, Andres Mejia <mcitadel@gmail.com>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/5/07, Miriam Ruiz wrote:
> You mean to apply patches conditionally depending on which version of boost
> it is compiling against?
Yes, as libboost_python.so doesn't exist anymore after
libboost-python-dev 1.34. You have to use libboost_python-st.so and
thus -lboost_python-st instead.
> That seems a bit wierd, would we fhave to upgrade
> the packahe with every new version of boost out there?
Looking at http://bugs.debian.org/424038, I don't think we'll have to.
Seems that from now on, -lboost_python-st (the default) or
-lboost_python-mt will have to be used.
> Isn't there a better solution?
As far as searching for the correct library depending on what version
of libboost-python-dev is being used? I'm afraid not. There's no
libboost_python-
st.so in earlier versions.
> What kind of errors do you get? I'm not sure I'm able to see the situation
See http://bugs.debian.org/426872
Andres Mejia
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org
iD8DBQFGZYJ4gsFbAuXxMZYRAhtBAKCT6Q59UT0VIvcuUSEOubMmfKotWwCgo2Qz
kbbFGDILkUXGHCP7EP3KyZI=
=AKoW
-----END PGP SIGNATURE-----
Reply to: