Issue 32484: ImportError for gdbm 1.14 (original) (raw)
Issue32484
Created on 2018-01-02 19:39 by sam-s, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (3) | ||
|---|---|---|
| msg309392 - (view) | Author: sds (sam-s) | Date: 2018-01-02 19:39 |
| After upgrading to gdbm stable 1.14, I get this: ``` >>> import gdbm Traceback (most recent call last): File "", line 1, in ImportError: dlopen(/.../lib/python2.7/lib-dynload/gdbm.so, 2): Symbol not found: _gdbm_errno Referenced from: /.../lib/python2.7/lib-dynload/gdbm.so Expected in: /usr/local/opt/gdbm/lib/libgdbm.4.dylib in /.../lib/python2.7/lib-dynload/gdbm.so ``` This is probably related to this change: ``` * Make gdbm_error global thread safe. ``` (https://lists.gnu.org/archive/html/info-gnu/2018-01/msg00000.html) | ||
| msg309398 - (view) | Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2018-01-03 07:13 |
| It seems like Python will need to be recompiled then. | ||
| msg309400 - (view) | Author: (yan12125) * | Date: 2018-01-03 07:36 |
| I can confirm a rebuild fixes _gdbm for Python 3.6.4. This is also a bug in gdbm - it should bump soname (gdbm.so.4 => gdbm.so.5) for such an ABI incompatibility. I've sent a report to gdbm developers. |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:56 | admin | set | github: 76665 |
| 2018-01-03 16:41:18 | benjamin.peterson | set | status: open -> closedresolution: third partystage: resolved |
| 2018-01-03 07:36:31 | yan12125 | set | messages: + |
| 2018-01-03 07:13:52 | benjamin.peterson | set | nosy: + benjamin.petersonmessages: + |
| 2018-01-03 03:26:12 | yan12125 | set | nosy: + yan12125 |
| 2018-01-02 19:39:18 | sam-s | create |