ue:
http://bugs.python.org/issue1628484
Bob and I are discussing the same thing, so if you want to help us in
this effort of making Python's build system more flexible and correct,
you're really welcome.
Regards,
--
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engine
e proposing
installing the header files in different places, right? Since these
files are the same (except for pyconfig.h, as you said), I assume that
the reason for this separation is only for safety. I'll consider your
proposal.
Regards,
--
Sérgio Durigan Júnior
Linux on Power Toolchain -
Some of them have patched Python to fit their
> needs. You may have to do that as well.
I'll sure take a look at them. Thanks!
--
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil
___
Py
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&#
#ifdef USE_64BIT" or
something on them.
Thanks,
--
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/pyth
hat
I've found, I only need to modify configure.in file (and maybe
Makefile.pre.in). Is that correct?
Regards,
--
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil
___
Python-Dev mailing l
ds to $BASECFLAGS the string '-m64'. It seems
to be more than that, though (because that approach didn't work
completely)... Can anyone give me a hand on this? As far as I could
investigate, I must change setup.py in order to get this issue fixed,
right?
Thanks in advance,
--
Sérgio Duri
