Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment:
On Tue, 2008-04-15 at 02:01 +, Bob Atkins wrote:
> I don't know why you are resisting this change. I took the time to
> report the bug, proposed a fix /_*and*_/ contributed the patch that
> would make the
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment:
Hi Martin,
On Mon, 2008-04-14 at 20:04 +, Martin v. Löwis wrote:
> Martin v. Löwis <[EMAIL PROTECTED]> added the comment:
>
> > This is what you get when you try to build a 64-bit Python on a biarch
> &
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment:
Hi Martin,
This is what you get when you try to build a 64-bit Python on a biarch
machine (64-bit kernel, 32-bit userspace), using a gcc that generates
natively 32-bit objects (therefore, you *must* pass the '-m64'
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment:
Hi,
Continuing with my effort to improve Python's build system, I'd really
like to know why this issue has not been solved yet. I mean, apparently
this problem is still present in Python 2.5, since I can't chan
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment:
Hi Martin,
Actually, I know that you can use CC to do it, but IMHO that's not the
correct approach. I understand too you concern about adding @CFLAGS@,
but I think the user should be able to define his/her own CFLAGS, and
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment:
Hi Martin,
Thanks for your quick answer. I'd like to know what can we do to push
this patch into upstream. Does the fact that the patch is posted in a
bug report (and not in a developer's mailing list) is slowing do
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment:
Hi,
I'd like to know the status of this issue. I'm having the same problems
here with PPC64, and the patch that Bob Atkins has sent works fine for
me too. Would you intend to apply this patch in upstream?
T
