lib_pypy/gdbm.py: package.py produces binary on OS X with hard-coded path
Created originally on Bitbucket by Former user
Prior to CFFI 1.0, gdbm.py would be compiled on first import of the module on OS X, causing either a descriptive exception or a successful compilation against the user's installed version.
However, OS X does not ship with GDBM, one must install if from Homebrew (/usr/local/lib), MacPorts (/opt/local/lib), pkgsrc (/usr/pkg/lib) or one of the various custom binaries around. A subsequent run of package.py will produce a gdbm.so with a load command hard-wired to the path to GDBM on the build machine.
Perhaps consider disabling static compilation of GDBM on OS X? I think the remaining alternative is to require a specific GDBM distribution, or bundle GDBM with PyPy, which probably presents some fun licensing issue.