Bugs item #435455, was opened at 2001-06-22 06:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=435455&group_id=5470
Category: Distutils
Group: Platform-specific
Status: Closed
Resolution: Wont Fix
Priority: 5
Submitted By: Ole H. Nielsen (ohnielse)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.0.1c1 fails to build on RH7.1
Initial Comment:
Building Python 2.0.1c1 on a RedHat 7.1 (2.4.2-2 on
i586) fails at this point:
cd Modules; make OPT="-g -O2 -Wall -Wstrict-prototypes
-fPIC" VERSION="2.0" \
prefix="/usr/local"
exec_prefix="/usr/local" \
sharedmods
make[1]: Entering directory
`/scratch/ohnielse/Python-2.0.1/Modules'
gcc -fpic -g -O2 -Wall -Wstrict-prototypes -fPIC
-I./../Include -I.. -DHAVE_CONFIG_H -c ./bsddbmodule.c
./bsddbmodule.c: In function `newdbhashobject':
./bsddbmodule.c:55: `HASHINFO' undeclared (first use in
this function)
./bsddbmodule.c:55: (Each undeclared identifier is
reported only once
./bsddbmodule.c:55: for each function it appears in.)
./bsddbmodule.c:55: parse error before `info'
./bsddbmodule.c:60: `info' undeclared (first use in
this function)
./bsddbmodule.c:71: warning: implicit declaration of
function `dbopen'
./bsddbmodule.c:71: warning: assignment makes pointer
from integer without a cast
./bsddbmodule.c: In function `newdbbtobject':
./bsddbmodule.c:100: `BTREEINFO' undeclared (first use
in this function)
./bsddbmodule.c:100: parse error before `info'
./bsddbmodule.c:105: `info' undeclared (first use in
this function)
./bsddbmodule.c:118: warning: assignment makes pointer
from integer without a cast
./bsddbmodule.c: In function `newdbrnobject':
./bsddbmodule.c:147: `RECNOINFO' undeclared (first use
in this function)
./bsddbmodule.c:147: parse error before `info'
./bsddbmodule.c:152: `info' undeclared (first use in
this function)
./bsddbmodule.c:164: warning: assignment makes pointer
from integer without a cast
./bsddbmodule.c: In function `bsddb_dealloc':
./bsddbmodule.c:202: too few arguments to function
./bsddbmodule.c: In function `bsddb_length':
./bsddbmodule.c:232: structure has no member named
`seq'
./bsddbmodule.c:233: `R_FIRST' undeclared (first use in
this function)
./bsddbmodule.c:235: structure has no member named
`seq'
./bsddbmodule.c:236: `R_NEXT' undeclared (first use in
this function)
./bsddbmodule.c:229: warning: `status' might be used
uninitialized in this function
./bsddbmodule.c: In function `bsddb_subscript':
./bsddbmodule.c:265: warning: passing arg 2 of pointer
to function from incompatible pointer type
./bsddbmodule.c:265: too few arguments to function
./bsddbmodule.c: In function `bsddb_ass_sub':
./bsddbmodule.c:307: warning: passing arg 2 of pointer
to function from incompatible pointer type
./bsddbmodule.c:307: too few arguments to function
./bsddbmodule.c:330: warning: passing arg 2 of pointer
to function from incompatible pointer type
./bsddbmodule.c:330: too few arguments to function
./bsddbmodule.c: In function `bsddb_close':
./bsddbmodule.c:357: too few arguments to function
./bsddbmodule.c: In function `bsddb_keys':
./bsddbmodule.c:386: structure has no member named
`seq'
./bsddbmodule.c:386: `R_FIRST' undeclared (first use in
this function)
./bsddbmodule.c:407: structure has no member named
`seq'
./bsddbmodule.c:407: `R_NEXT' undeclared (first use in
this function)
./bsddbmodule.c:376: warning: `status' might be used
uninitialized in this function
./bsddbmodule.c: In function `bsddb_has_key':
./bsddbmodule.c:440: warning: passing arg 2 of pointer
to function from incompatible pointer type
./bsddbmodule.c:440: too few arguments to function
./bsddbmodule.c: In function `bsddb_set_location':
./bsddbmodule.c:466: structure has no member named
`seq'
./bsddbmodule.c:466: `R_CURSOR' undeclared (first use
in this function)
./bsddbmodule.c:453: warning: `status' might be used
uninitialized in this function
./bsddbmodule.c: In function `bsddb_seq':
./bsddbmodule.c:503: structure has no member named
`seq'
./bsddbmodule.c:489: warning: `status' might be used
uninitialized in this function
./bsddbmodule.c: In function `bsddb_next':
./bsddbmodule.c:531: `R_NEXT' undeclared (first use in
this function)
./bsddbmodule.c: In function `bsddb_previous':
./bsddbmodule.c:536: `R_PREV' undeclared (first use in
this function)
./bsddbmodule.c: In function `bsddb_first':
./bsddbmodule.c:541: `R_FIRST' undeclared (first use in
this function)
./bsddbmodule.c: In function `bsddb_last':
./bsddbmodule.c:546: `R_LAST' undeclared (first use in
this function)
make[1]: *** [bsddbmodule.o] Error 1
----------------------------------------------------------------------
Comment By: Erik Andersén (erik_andersen)
Date: 2001-10-31 11:09
Message:
Logged In: YES
user_id=364358
In Modules/bsddbmodule.c change
#ifdef HAVE_DB_185_H
#include <db_185.h>
#else
#include <db.h>
#endif
to
#include <db3/db_185.h>
Erik Andersen
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2001-10-01 03:17
Message:
Logged In: YES
user_id=21627
Since it is unlikely that we'll get further analysis on the
cause of this problem, I'm closing the report now. Please
try one of the 2.2 prereleases; if problems remain, please
report them in a new bug report.
----------------------------------------------------------------------
Comment By: Thomas Wouters (twouters)
Date: 2001-09-06 05:25
Message:
Logged In: YES
user_id=34209
Okay, unassigning. Why I had it ? unsure. It probably
dates back from the time I still had a RedHat box. I
swapped them all with Debian and I live a much happier
life as a result :-)
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2001-09-05 11:25
Message:
Logged In: YES
user_id=6380
Can someone see if this is still a problem with current CVS
(or even with 2.2a2)? I believe we've added another layer of
patchwork around the bsddb compilation in setup.py.
Why does Thomas own this item? Thomas, if you don't want
it, feel free to unassign it.
----------------------------------------------------------------------
Comment By: Sjoerd Mullender (sjoerd)
Date: 2001-07-10 01:30
Message:
Logged In: YES
user_id=43607
I have no trouble building the current CVS version on RedHat
7.1. However, when I try the gcc command given in the error
message, I get much the same errors.
The deciding difference was: setup.py (part of the standard
current build process) adds -DHAVE_DB_185_H=1 to the
compiler command line.
----------------------------------------------------------------------
Comment By: Ole H. Nielsen (ohnielse)
Date: 2001-07-09 07:51
Message:
Logged In: YES
user_id=27232
twouters wrote:
> I suspect the problem here is that you don't have the
> appropriate -devel RPM installed. I think you need
> 'db3-devel', but 'db2-devel', 'db1-devel' or 'db-devel'
> might work too.
Sorry, no. These RPMs seem to be installed by default on RedHat 7.1:
# rpm -qa | grep devel | grep db
db1-devel-1.85-5
db2-devel-2.4.14-5
gdbm-devel-1.8.0-5
db3-devel-3.1.17-7
It would be nice if a Python developer could gain access to a RedHat 7.1
machine to sort this problem out :-)
----------------------------------------------------------------------
Comment By: Thomas Wouters (twouters)
Date: 2001-07-09 07:06
Message:
Logged In: YES
user_id=34209
I suspect the problem here is that you don't have the
appropriate -devel RPM installed. I think you need
'db3-devel', but 'db2-devel', 'db1-devel' or 'db-devel'
might work too.
Can you confirm that you have none of those installed ? I
think what happens is that distutils can't find an include
header to include, so it assumes the DB implementation is
included in libc, instead. (Changing catagory to distutils
on that assumption.)
----------------------------------------------------------------------
Comment By: Ole H. Nielsen (ohnielse)
Date: 2001-06-26 14:52
Message:
Logged In: YES
user_id=27232
loewis wrote:
> I have asked you to report things, not to change things.
> It is not easy to repeat for me, as I don't have Redhat
7.1.
Sorry about the confusion. My report is for RedHat 7.1:
1. Untar the distribution 2.0.1c1
2. ./configure
3. make
The errors reported occur. I have changed nothing.
I don't know what bsddb is, nor why it's getting compiled.
Hopefully, someone knowing Python 2.0.1 and having
access to a RedHat 7.1 box could look into the problem.
At this point Python building seems broken on RH7.1 :-(
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2001-06-26 00:02
Message:
Logged In: YES
user_id=21627
I have asked you to report things, not to change things. It
is not easy to repeat for me, as I don't have Redhat 7.1.
----------------------------------------------------------------------
Comment By: Ole H. Nielsen (ohnielse)
Date: 2001-06-25 15:20
Message:
Logged In: YES
user_id=27232
loewis wrote:
> Please report the following things:
> - the line in Setup that you activated to enable
> compilation of bsddb
> - the exact version of the bsddb RPM package that
provides
> db.h
> - whether or not this packages includes a file db_185.h
Sorry, I didn't change ANYTHING ! I was trying a vanilla
build on RedHat 7.1 ! Should be easy to repeat...
Maybe the build scripts make some incorrect choices
on RedHat 7.1 ?
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2001-06-23 13:58
Message:
Logged In: YES
user_id=21627
Please report the following things:
- the line in Setup that you activated to enable
compilation of bsddb
- the exact version of the bsddb RPM package that provides
db.h
- whether or not this packages includes a file db_185.h
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=435455&group_id=5470
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4