Boost Testing :
From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2005-11-21 22:47:12
I reinstalled bz2 library in /usr/local, rebuilt python and the problem
with bz2 module disappeared. I did not run regression.py, I'll do it
tomorrow, but 'import bz2' works.
Previously, the bz2 library was installed in directory which was not
part of the PATH. I'm pretty sure, it was the problem.
Thanks for the help!
----- Original Message -----
From: "Markus Schöpflin" <markus.schoepflin_at_[hidden]>
Sent: Sunday, November 20, 2005 6:03 AM
Subject: Re: [Boost-testing] "bz2 module is not available"
> Boris Gubenko wrote:
>> What, I think, is happening is: bz2 module is based on bz2module.c.The
>> ..c module requires header bzlib.h which is not on the include path --
>> this header does not come with python distribution, it is part of bzip2
>> distribution. As a result, bz2 module was not built and autodetecting
>> script setup.py did not add it as extension. From the script:
>> # Gustavo Niemeyer's bz2 module.
>> if (self.compiler.find_library_file(lib_dirs, 'bz2')):
>> exts.append( Extension('bz2', ['bz2module.c'],
>> libraries = ['bz2']) )
>> I'll check this theory on Monday by putting bzlib.h on the include path
>> (cannot log onto testdrive machine now). If configure still does not
>> add bz2module.c to the makefile, I'll try to add it to Modules/Setup.
> Yes, you're right, bz2 support in python requires the bz2 lib to be
> installed. But from the source code above, it seems that it scans the
> library dirs looking for the lib and not for the header file. I'm sure
> there is a configure option to add additional dirs to the lib search
> path. Maybe you should try this.
> HTH, Markus
> Boost-Testing mailing list