[pkg-boost-devel] Boost and Python 2.4
Steve M. Robbins
steve at sumost.ca
Mon Aug 13 19:44:52 UTC 2007
On Mon, Aug 13, 2007 at 08:47:40AM +0200, Domenico Andreoli wrote:
> On Mon, Aug 13, 2007 at 01:22:33AM -0500, Steve M. Robbins wrote:
> > On Mon, Aug 13, 2007 at 02:03:55AM +0200, Domenico Andreoli wrote:
> > > it was required to change the soname, I would prefer to change the
> > > python 2.4 one, which is anyway going away probably before lenny.
> >
> > I think there's nearly always 2 or more python versions officially
> > supported in Debian. So it makes sense to decorate the Boost.Python
> > lib name and SONAME with the python version at all times, don't you
> > think?
>
> losing binary compatibility with other distributions, if any?
I don't see any better option at present. I don't think we have
binary compatibility in any case. Imagine if our 1.34.1 Boost.Python
library is linked to Python 2.4 and theirs is linked to 2.5.
> > P.S. I "corrected" the
> > $(bjam): CC=gcc-4.1
> > line in the diff without really understanding it. What does
> > it mean to have a variable assignment as a dependency of a
> > target? Shouldn't this be a straight variable assignment?
> > Does CC need to be assigned?
>
> that sets CC only fot the $(bjam) target, where it used by the cc
> toolset, the one used to build bjam.
>
> it is required to explicitly build bjam with gcc 4.1 instead of the
> default compiler version, in case it changes to 4.2 in the meanwhile. see
> the patch from ubuntu.
Ah ok. Let's add a comment to debian/rules, then, as to why we're
doing this. Also, would it be clearer to use the following?
$(bjam):
CC=gcc-4.1 cd tools/jam/src && sh build.sh cc && mv bin.*/bjam .
Cheers,
-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-boost-devel/attachments/20070813/c8b918bc/attachment.pgp
More information about the pkg-boost-devel
mailing list