[issue2936] ctypes.util.find_library() doesn't consult LD_LIBRARY_PATH

[Bill Janssen]

Bill Janssen <bill.janssen at gmail.com> added the comment:

The question is, which linker?  I think it should be ld.so, which links "on
demand", and does pay attention to LD_LIBRARY_PATH.  I'm not sure what the
point of find_library() is, otherwise.

Bill

On Thu, May 29, 2008 at 11:24 AM, Thomas Heller <report at bugs.python.org>
wrote:

>
> Thomas Heller <theller at ctypes.org> added the comment:
>
> To be honest,  I do not understand this request and the discussion.
> ctypes.util.find_library(), as dcumented, is supposed to simulate what
> the linker does:  find the name of a shared library.  For example,
> it returns 'libc.so.6' when called as ctypes.util.find_library('c').
> AFAIK (and I don't know very much about posix shared libs or linkers)
> the linker does not pay attention to (DY)LD_LIBRARY_PATH env var.
>
> dlopen(shared-lib-name) does use this env vars, but this behaviour is
> already built into dlopen.
>
> ----------
> assignee:  -> theller
> nosy: +theller
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue2936>
> _______________________________________
>

Added file: http://bugs.python.org/file10476/unnamed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue2936>
_______________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: unnamed
URL: <http://mail.python.org/pipermail/python-bugs-list/attachments/20080530/3f7b89a2/attachment.txt>