[Python-bugs-list] [Bug #117508] Building 2.0 under Solaris 8 with GCC 2.95.2 fails to link

[noreply@sourceforge.net]

Bug #117508, was updated on 2000-Oct-23 10:16
Here is a current snapshot of the bug.

Project: Python
Category: Build
Status: Open
Resolution: None
Bug Group: Platform-specific
Priority: 6
Summary: Building 2.0 under Solaris 8 with GCC 2.95.2 fails to link

Details: With no special options to 'configure' the final link step results in

   cd Modules;  make OPT="-g -O2 -Wall -Wstrict-prototypes" VERSION="2.0" \
                   prefix="/usr/local" exec_prefix="/usr/local" \
                   LIBRARY=../libpython2.0.a link
   make[1]: Entering directory `/tmp/pedwards/newbuild/Python-2.0/Modules'
   gcc   python.o \
             ../libpython2.0.a -ldb                                 -lpthread -lsocket -lnsl -ldl  -lthread -lm  -o python 
   Undefined                       first referenced
    symbol                             in file
   dbopen                              ../libpython2.0.a(bsddbmodule.o)
   ld: fatal: Symbol referencing errors. No output written to python
   collect2: ld returned 1 exit status
   make[1]: *** [link] Error 1

This is using GNU make, and GCC with the native linker.  Using the native
compiler works fine.  



Follow-Ups:

Date: 2000-Oct-28 03:50
By: loewis

Comment:
It appears that configure detected the presence of db.h on your system, perhaps in /usr/local. Do you have a BSDDB installation there? Could it be that this installation is somehow corrupted (e.g. that the db.h header does not match the libdb.a library?). That would explain why the native compiler has no problems - it simply doesn't see the db.h header in /usr/local, so it doesn't even attempt to build bsddbmodule.o.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=117508&group_id=5470