[issue4861] fix problems with ctypes.util.find_library

Martin Panter added the comment: FYI the OSError exceptions added here were never triggered as intended, and they are proposed to be removed as part of Issue 25751. -- nosy: +martin.panter ___ Python tracker __

[issue4861] fix problems with ctypes.util.find_library

Matthias Klose added the comment: now fixed in 2.6, 2.7, 3.0 and 3.1. objdump is never installed in /sbin. I don't think we should assume a specific path for objdump. we don't do this for gcc either. -- assignee: theller -> doko resolution: -> fixed status: open -> closed ___

[issue4861] fix problems with ctypes.util.find_library

Jean-Paul Calderone added the comment: This seems to be a partial duplicate of 3383. A suggestion on that ticket was to look for objdump in PATH and then try /usr/sbin. -- nosy: +exarkun ___ Python tracker ___

[issue4861] fix problems with ctypes.util.find_library

Matthias Klose added the comment: new version of the patch using os instead of platform, and selecting the correct library for biarch platforms, tested on ia64, sparc, s390, amd64, ppc64. unsure if there's a better way to find out if the executable is 32 or 64bit. Added file: http://bugs.python

[issue4861] fix problems with ctypes.util.find_library

Thomas Heller added the comment: Matthias Klose schrieb: > there are some problems with ctypes.util.find_library(), which I would > like to see fixed on active branches. > > - find_library is not robust, if either objdump or gcc are not >installed. fixed by raising an exception if the tool

[issue4861] fix problems with ctypes.util.find_library

New submission from Matthias Klose : there are some problems with ctypes.util.find_library(), which I would like to see fixed on active branches. - find_library is not robust, if either objdump or gcc are not installed. fixed by raising an exception if the tools are not found. Is OSError