Change History (8)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Summary: | Phyton-2.6 → Python-2.6.1 |
Fixed at revision 7695.
comment:4 by , 16 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
We apply the " Python-2.6.1-gdbm-1.patch" to fix a build issue with gdbm (according with the headers), but I can't reproduce the error, see:
building 'gdbm' extension gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -I/tmp/Python-2.6.1/./Include -I. -IInclude -I./Include -I/usr/local/include -I/tmp/Python-2.6.1/Include -I/tmp/Python-2.6.1 -c /tmp/Python-2.6.1/Modules/gdbmmodule.c -o build/temp.linux-i686-2.6/tmp/Python-2.6.1/Modules/gdbmmodule.o gcc -pthread -shared -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes build/temp.linux-i686-2.6/tmp/Python-2.6.1/Modules/gdbmmodule.o -L/usr/local/lib -L. -lgdbm -lpython2.6 -o build/lib.linux-i686-2.6/gdbm.so
Reopening for confirmation.
comment:5 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
When I do it without the patch, the end of the make gives:
Failed to build these modules: dbm
With the patch the dbm module is built.
comment:6 by , 16 years ago
Ah ok, so you don't have gdbm installed.
In any case, the name of the patch and the headers are misleading.
"Description: Fixes Python build issue with gdbm"
Note that upstream gives precedence to gdbm over bdb (if both are found).
comment:7 by , 16 years ago
But I do have gdbm installed. If I didn't there wouldn't be a need for the patch. The description is accurate AFAICT.
New version 2.6.1. A bugfix release.