I've been upgrading a few machines to Redhat 9 from 7.3 and I've run into a few minor problems with Python on the 2.2 maint branch. Both dbmmodule and _socket fail to build properly. Neither problems exist in 2.3 cvs. The socket problem is fairly shallow I think: including ssl.h eventually includes krb5.h. Python 2.3's setup.py has a couple of lines of code to deal with this, and that just needs to go into 2.2 maint's setup.py, so I checked this in. The dbm problem is just a bit deeper. dbm ends up linking against gdbm, so the library has to be specified in setup.py. I'm nervous about adding the stuff to setup.py because I don't want to break other platforms. Looking at 2.3's setup.py shows this section to be more complicated and I'm too tired to tease everything out tonight. I'll attach a diff to this message in case anybody else feels like mucking with it in the meantime. -Barry
Barry Warsaw <barry@python.org> writes:
- exts.append( Extension('dbm', ['dbmmodule.c']) ) + exts.append( Extension('dbm', ['dbmmodule.c'], + libraries = ['gdbm']) )
I think this was an alternative for platforms where a dbm library is part of the C library. Your patch would kill those platforms - but it may be that we are talking about the empty set here. Regards, Martin
On Sun, Apr 27, 2003 at 10:22:53AM +0200, Martin v. Löwis wrote:
Barry Warsaw <barry@python.org> writes:
- exts.append( Extension('dbm', ['dbmmodule.c']) ) + exts.append( Extension('dbm', ['dbmmodule.c'], + libraries = ['gdbm']) )
I think this was an alternative for platforms where a dbm library is part of the C library. Your patch would kill those platforms - but it may be that we are talking about the empty set here.
In either case, it should only link to gdbm if gdbm exists -- which is checked for right below the patch. -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
participants (3)
-
Barry Warsaw -
martin＠v.loewis.de -
Thomas Wouters