[pypy-issue] Issue #2050: `package.py` doesn't have `--without-gdbm` option (pypy/pypy)

posita issues-reply at bitbucket.org
Fri May 22 06:02:43 CEST 2015

New issue 2050: `package.py` doesn't have `--without-gdbm` option


I'm trying to package PyPy without gdbm. `package.py` recommends using the `--without-gdbm` option to suppress the error.

% ./pypy-c pypy/tool/release/package.py --override_pypy_c ./pypy-c
lib_pypy/__pycache__/_cffi__gc4433c0bxb981b228.c:53:22: fatal error: gdbm.h: No such file or directory
     #include "gdbm.h"
compilation terminated.
Traceback (most recent call last):
  File "<builtin>/app_main.py", line 75, in run_toplevel
  File "<builtin>/app_main.py", line 588, in run_it
  File "<string>", line 1, in <module>
  File "/tmp/build/pypy-2.5.1-src/lib_pypy/gdbm.py", line 69, in <module>
    raise ImportError('%s: %s' %(e.__class__.__name__, e))
ImportError: VerificationError: CompileError: command 'cc' failed with exit status 1
Building gdbm bindings failed.
You can either install development headers package or
add --without-gdbm option to skip packaging binary CFFI extension.
% echo $?

But you can't use it:

% ./pypy-c pypy/tool/release/package.py --override_pypy_c ./pypy-c --without-gdbm
usage: package.py [-h] [--without-tk] [--without-cffi] [--nostrip]
                  [--rename_pypy_c PYPY_C] [--archive-name NAME]
                  [--builddir BUILDDIR] [--targetdir TARGETDIR]
                  [--override_pypy_c OVERRIDE_PYPY_C]
package.py: error: unrecognized arguments: --without-gdbm

It looks like only `tk` and `cffi` can be excluded.

More information about the pypy-issue mailing list