On Thu, 2013-11-14 at 10:36 -0800, Ned Deily wrote:
> In article <1384442536.3496.532.camel@pdsdesk>,
> Paul Smith 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 direc
In article <1384442536.3496.532.camel@pdsdesk>,
Paul Smith 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 flags or
> whateve
On Wed, 2013-11-13 at 23:06 -0800, Ned Deily wrote:
> On Nov 13, 2013, at 17:24 , Paul Smith 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 :-).
>
> Well, i
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 problemat
On Nov 13, 2013, at 17:24 , Paul Smith 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 ability to copy
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
On Nov 13, 2013, at 14:59 , Paul Smith 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:
>> - Avoid --enabl
In article ,
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 ways
> things can go wrong. If you've built with
In article <1384370183.3496.472.camel@pdsdesk>,
Paul Smith 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:
>
> $ configure --prefix
