Message67516
| Author |
janssen |
| Recipients |
janssen, jcea, schmir, theller |
| Date |
2008年05月30日.01:08:49 |
| SpamBayes Score |
0.002781923 |
| Marked as misclassified |
No |
| Message-id |
<4b3e516a0805291808h2200dd4bj223532c7f7ee61da@mail.gmail.com> |
| In-reply-to |
<1212085463.91.0.216097866229.issue2936@psf.upfronthosting.co.za> |
| Content |
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@bugs.python.org>
wrote:
>
> Thomas Heller <theller@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@bugs.python.org>
> <http://bugs.python.org/issue2936>
> _______________________________________
> |
| Files |
| File name |
Uploaded |
|
unnamed
|
janssen,
2008年05月30日.01:08:47
|
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2008年05月30日 01:08:52 | janssen | set | spambayes_score: 0.00278192 -> 0.002781923 recipients:
+ janssen, theller, jcea, schmir |
| 2008年05月30日 01:08:49 | janssen | link | issue2936 messages |
| 2008年05月30日 01:08:49 | janssen | create |
|