Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-15 Thread Paul Smith
On Thu, 2013-11-14 at 10:36 -0800, Ned Deily wrote: In article 1384442536.3496.532.camel@pdsdesk, Paul Smith p...@mad-scientist.net wrote: [...] By relocatable I mean runnable from any location; i.e., not fixed. I have a wrapper around the Python executable that can compute the correct

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-14 Thread Paul Smith
On Wed, 2013-11-13 at 23:06 -0800, Ned Deily wrote: On Nov 13, 2013, at 17:24 , Paul Smith p...@mad-scientist.net wrote: I'm discovering that this is tricky. I don't want to bring OS wars into it, but this kind of thing is so simple and just works on GNU/Linux. I guess I've been spoiled

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-14 Thread Ned Deily
In article 1384442536.3496.532.camel@pdsdesk, Paul Smith p...@mad-scientist.net wrote: [...] By relocatable I mean runnable from any location; i.e., not fixed. I have a wrapper around the Python executable that can compute the correct root directory and set any environment variables or add

python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Paul Smith
Hi all. I need to build my own version of Python on a MacOSX system, and I can't seem to do it successfully. I need to build it with a particular location, etc. and so I can't use Homebrew or whatever: I need to compile it myself from the source tarball. I did look through the Homebrew recipe

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Ned Deily
In article 1384370183.3496.472.camel@pdsdesk, Paul Smith p...@mad-scientist.net wrote: I'm using MacOSX 10.7.5 with xcode 4.1, containing gcc 4.2.1 / clang 2.1 (configure seems to choose gcc). I've tried this with both Python 2.7.5 and 2.7.6. I get the tarball, unpack it, then: $

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Ned Deily
In article nad-e7cc3b.14401113112...@news.gmane.org, Ned Deily n...@acm.org wrote: There shouldn't be any problems with what you are trying to do. It works for me with Python 2.7.6 and pycrypto-2.6.1. Some suggestions: - Avoid --enable-shared on OS X at least initially. There are too many

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Ned Deily
On Nov 13, 2013, at 14:59 , Paul Smith p...@mad-scientist.net wrote: Thanks for the response Ned! On Wed, 2013-11-13 at 14:40 -0800, Ned Deily wrote: There shouldn't be any problems with what you are trying to do. It works for me with Python 2.7.6 and pycrypto-2.6.1. Some suggestions: -

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Paul Smith
Thanks for the response Ned! On Wed, 2013-11-13 at 14:40 -0800, Ned Deily wrote: There shouldn't be any problems with what you are trying to do. It works for me with Python 2.7.6 and pycrypto-2.6.1. Some suggestions: - Avoid --enable-shared on OS X at least initially. There are too many

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Ned Deily
On Nov 13, 2013, at 17:24 , Paul Smith p...@mad-scientist.net wrote: On Wed, 2013-11-13 at 16:00 -0800, Ned Deily wrote: The reason I've set PYTHONHOME is ultimately I need this installation to be relocatable. It's going to be shared across lots of different systems and they'll have the

Re: python 2.7.x on MacOSX: failed dlopen() on .so's

2013-11-13 Thread Paul Smith
On Wed, 2013-11-13 at 16:00 -0800, Ned Deily wrote: The reason I've set PYTHONHOME is ultimately I need this installation to be relocatable. It's going to be shared across lots of different systems and they'll have the ability to copy it wherever they want. That could be problematic. You