In article ,
Paul Smith wrote:
>One thing I always liked about Perl was the way you can create a single
>installation directory which can be shared between archictures. Say
>what you will about the language: the Porters have an enormous amount of
>experience and expertise producing portable and
On Sun, 2013-11-17 at 10:46 -0500, Paul Smith wrote:
> Unfortunately, if you set PYTHONHOME then it's used for both $PREFIX and
> $EXECPREFIX without any path probing whatsoever, so PYTHONHOME is
> unusable with an installation where you've used different values for
> --prefix and --exec-prefix dur
On Mon, Nov 18, 2013 at 2:46 AM, Paul Smith wrote:
> However, that configuration doesn't work
> for embedded Python (for example, if you embed the Python interpreter in
> GDB by linking libpython2.7.a) if you relocate it.
> ...
> I'm willing to do this and file a bug with a patch if there's any
>
On Sat, 2013-11-16 at 19:28 -0500, Paul Smith wrote:
> On Fri, 2013-11-15 at 18:00 -0500, Paul Smith wrote:
> > By this I mean, basically, multiple architectures (Linux, Solaris,
> > MacOSX, even Windows) sharing the same $prefix/lib/python2.7 directory.
> > The large majority of the contents there
On Fri, 2013-11-15 at 18:00 -0500, Paul Smith wrote:
> By this I mean, basically, multiple architectures (Linux, Solaris,
> MacOSX, even Windows) sharing the same $prefix/lib/python2.7 directory.
> The large majority of the contents there are completely portable across
> architectures (aren't they?
One thing I always liked about Perl was the way you can create a single
installation directory which can be shared between archictures. Say
what you will about the language: the Porters have an enormous amount of
experience and expertise producing portable and flexible interpreter
installations.
