[Python-bugs-list] [Bug #117464] clash with BSD db when building
noreply@sourceforge.net
noreply@sourceforge.net
Tue, 12 Dec 2000 13:11:56 -0800
Bug #117464, was updated on 2000-Oct-23 00:29
Here is a current snapshot of the bug.
Project: Python
Category: Build
Status: Open
Resolution: None
Bug Group: Platform-specific
Priority: 5
Submitted by: fleury
Assigned to : nobody
Summary: clash with BSD db when building
Details: On RH7.0, beside the LONG_BIT issue, I came across a db.h missmatch.
The preprocessor directive values used in bsddbmodule.c correspond to the /usr/include/db1/db.h file, but on my system, /usr/include/db.h points to db3/db.h which does not define the same set of values, and does not compile.
Compiling with the old file works, but obviously it does not link...
configure (with no options) ran trouble free.
The system is:
RedHat 7.0
gcc version 2.96 20000731 (yes with the LONG_BIT problem)
Python 2.0 final release
Regards,
Pascal
Follow-Ups:
Date: 2000-Nov-06 08:40
By: montanaro
Comment:
This is going to require a bit of effort. My current scheme for detecting whether bsddb can be built/linked or not relies on the presence or absence of db.h and/or db_185.h. If db_185.h is present, libdb v.2 is assumed. If only db.h is present, libdb v.1 is assumed.
Now Sleepycat has libdb v.3, and on RH7 it appears you can have all three versions installed at once. I don't yet know if bsddbmodule.c can be built/linked with v.3 (seems likely, since db_185.h still existts), but even if it can, configure will have to grovel around in db.h looking for DB_VERSION_MAJOR. If it doesn't exist, we have v.1. If it does exist, its value will determine what version > 1 we have.
I imagine for an autoconf whiz this will be a simple task, but it's more of a challenge than I have time for at the moment. Anyone want to take this on?
-------------------------------------------------------
Date: 2000-Oct-23 18:13
By: fleury
Comment:
Well, I also tried at home, where I have a vanilla RH7.0 and it compiles perfectly.
The reported bug was on a RH6.2->RH7.0 upgraded machine.
-------------------------------------------------------
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=117464&group_id=5470