RetroSearch Browse

Fri Apr 11 20:21:44 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-April/078567.html

Hi Lemburg,

On Fri, 2008-04-11 at 19:38 +0200, M.-A. Lemburg wrote:
> On 2008-04-11 19:10, Sérgio Durigan Júnior wrote:
> > Hi all,
> > 
> > My question is simple: is there any problem when installing/using both
> > 32- and 64-bit Python's on the same machine? I'm more concerned about
> > header files (those installed under /usr/include/python-2.x), because as
> > far as I could see there's nothing similar to a "#ifdef USE_64BIT" or
> > something on them.
> 
> The include files are all static and can be used on both 32-bit and
> 64-bit platforms or installations.

Thanks :-).

> Only the /usr/lib/python2.x files differ between 32-bit and 64-bit
> (the configuration files are in /usr/lib/python2.x/config).

Hmm, right. I tried to modify the installation path (using --libdir
in ./configure) to /usr/lib64, but some *.pyo objects still are
installed under /usr/lib. AFAIK, these objects are bitness-dependent
(i.e., if they were generated by a 32-bit Python, they can only be
execute by a 32-bit Python - and vice-versa), right?

Is there any way to separate these arch-dependent files in /usr/lib
and /usr/lib64 depending on their bitness?

Thanks,

P.S.: I think this "misbehaviour" of --libdir is a bug. IMHO, it should
put every arch-dependent file in the path that the user provided.

-- 
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-April/078567.html below:

[Python-Dev] Python 32- and 64-bit living together