Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-09-29 07:03:24

On Friday 29 September 2006 13:56, Markus Schöpflin wrote:

> > Python is already linked with libz on those platforms where it's
> > required.
> So the explanation why it works at Comsoft but not at HP TestDrive, which
> are the same platform, is that at HP the libpython2.4.a somehow contains
> references to libz and at Comsoft it doesn't.
> HP:
> > nm libpython2.4.a | grep adler32
> adler32 | 0000000000000000 | U | 0000000000000008
> Comsoft:
> > nm libpython2.4.a | grep adler32
> Ok, I think I understood that now. This difference probably results from
> the fact that when compiling python at the TestDrive machine I linked libz
> statically, but not when compiling at Comsoft.
> Maybe I should change that, because the static libz will most probably not
> be found by the link process, as it's not installed in a standard location.

Is there some "standard" Python package for this system? We can add -lz, of
course, but the fact that python is built in different way on different boxes
is concerning.

If the "standard" Python lib includes libz inside it, then can you try
rebuilding Python and rerunning the tests?


Vladimir Prus
Boost.Build V2:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at