Re: [pypy-dev] dlopen NotImplementedError
Hmm, I'm thinking the dlopen error might be my problem. I think I built python at /root/pypy, and then moved it to a more proper location. But the error message is referring to /root/pypy, so I'm guessing it has that location hardcoded because that's where I built it? I'm going to rebuild but I wanted to post this message so that you guys don't worry about it (unless rebuilding doesn't help). -- Gary Robinson CTO Emergent Discovery, LLC personal email: garyrob@me.com work email: grobinson@emergentdiscovery.com Company: http://www.emergentdiscovery.com Blog: http://www.garyrobinson.net
On Wed, Dec 22, 2010 at 3:52 PM, Gary Robinson <garyrob@me.com> wrote:
Hmm, I'm thinking the dlopen error might be my problem. I think I built python at /root/pypy, and then moved it to a more proper location. But the error message is referring to /root/pypy, so I'm guessing it has that location hardcoded because that's where I built it?
I'm going to rebuild but I wanted to post this message so that you guys don't worry about it (unless rebuilding doesn't help).
--
Gary Robinson CTO Emergent Discovery, LLC personal email: garyrob@me.com work email: grobinson@emergentdiscovery.com Company: http://www.emergentdiscovery.com Blog: http://www.garyrobinson.net
_______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Nope, it's a known thing, anything trying to import ctypes on fast-forward blows up ATM. If anyone knows what dlopen(None) is supposed to mean, can they let me know and I'll try to take a pass at fixing this? Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me
On 09:54 pm, alex.gaynor@gmail.com wrote:
Hmm, I'm thinking the dlopen error might be my problem. I think I built python at /root/pypy, and then moved it to a more proper location. But the error message is referring to /root/pypy, so I'm guessing it has that location hardcoded because that's where I built it?
I'm going to rebuild but I wanted to post this message so that you guys don't worry about it (unless rebuilding doesn't help). Nope, it's a known thing, anything trying to import ctypes on fast- forward blows up ATM. If anyone knows what dlopen(None) is supposed to mean, can
On Wed, Dec 22, 2010 at 3:52 PM, Gary Robinson <garyrob@me.com> wrote: they let me know and I'll try to take a pass at fixing this?
From the dlopen man page: If filename is NULL, then the returned handle is for the main program. I imagine that's the case someone is trying to trigger with ctypes.LoadLibrary(None) (which is what the name `dlopen` is bound to in this context). On the other hand, maybe it's just a screw up somewhere else that causes None to show up instead of the right library name, I haven't looked at the code in question much. Jean-Paul
On Wed, Dec 22, 2010 at 4:41 PM, <exarkun@twistedmatrix.com> wrote:
On 09:54 pm, alex.gaynor@gmail.com wrote:
Hmm, I'm thinking the dlopen error might be my problem. I think I built python at /root/pypy, and then moved it to a more proper location. But the error message is referring to /root/pypy, so I'm guessing it has that location hardcoded because that's where I built it?
I'm going to rebuild but I wanted to post this message so that you guys don't worry about it (unless rebuilding doesn't help). Nope, it's a known thing, anything trying to import ctypes on fast- forward blows up ATM. If anyone knows what dlopen(None) is supposed to mean, can
On Wed, Dec 22, 2010 at 3:52 PM, Gary Robinson <garyrob@me.com> wrote: they let me know and I'll try to take a pass at fixing this?
From the dlopen man page:
If filename is NULL, then the returned handle is for the main program.
I imagine that's the case someone is trying to trigger with ctypes.LoadLibrary(None) (which is what the name `dlopen` is bound to in this context). On the other hand, maybe it's just a screw up somewhere else that causes None to show up instead of the right library name, I haven't looked at the code in question much.
Jean-Paul _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Ok I see the issue I think. It's coming from PyDLL(None). Not sure what the right solution is there, I know Amaury said he was working on the cpythonapi stuff. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me
CDLL(None) (or LoadLibrary(None)) is supposed to return to you the whole namespace (all loaded libraries). It's unsupported as far as I can tell. On Thu, Dec 23, 2010 at 12:45 AM, Alex Gaynor <alex.gaynor@gmail.com> wrote:
On Wed, Dec 22, 2010 at 4:41 PM, <exarkun@twistedmatrix.com> wrote:
On 09:54 pm, alex.gaynor@gmail.com wrote:
Hmm, I'm thinking the dlopen error might be my problem. I think I built python at /root/pypy, and then moved it to a more proper location. But the error message is referring to /root/pypy, so I'm guessing it has that location hardcoded because that's where I built it?
I'm going to rebuild but I wanted to post this message so that you guys don't worry about it (unless rebuilding doesn't help). Nope, it's a known thing, anything trying to import ctypes on fast- forward blows up ATM. If anyone knows what dlopen(None) is supposed to mean, can
On Wed, Dec 22, 2010 at 3:52 PM, Gary Robinson <garyrob@me.com> wrote: they let me know and I'll try to take a pass at fixing this?
From the dlopen man page:
If filename is NULL, then the returned handle is for the main program.
I imagine that's the case someone is trying to trigger with ctypes.LoadLibrary(None) (which is what the name `dlopen` is bound to in this context). On the other hand, maybe it's just a screw up somewhere else that causes None to show up instead of the right library name, I haven't looked at the code in question much.
Jean-Paul _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Ok I see the issue I think. It's coming from PyDLL(None). Not sure what the right solution is there, I know Amaury said he was working on the cpythonapi stuff.
Alex
-- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me
_______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Hi, 2010/12/23 Maciej Fijalkowski <fijall@gmail.com>
CDLL(None) (or LoadLibrary(None)) is supposed to return to you the whole namespace (all loaded libraries). It's unsupported as far as I can tell.
It should work by now (on Unix platforms of course). -- Amaury Forgeot d'Arc
participants (5)
-
Alex Gaynor -
Amaury Forgeot d'Arc -
exarkun＠twistedmatrix.com -
Gary Robinson -
Maciej Fijalkowski