> 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' option
> for the compiler):

Or you install an additional, different, C compiler that defaults to
AMD64.

> 1) As you could see above, actually you need CFLAGS in order to compile
> Python correctly. As far as I could investigate, the reason you need
> this is because of the tests that are done by configure. Without the
> CFLAGS, configure will think it's building a 32-bit Python, despite of
> the '-m64' flag in BASECFLAGS. So, do we need to propagate CFLAGS
> through Makefile or not? IMHO, we do.

Not necessarily. I think you can achieve the same effect by specifying
CC="gcc -m64" to configure.

> 2) Even with CFLAGS and BASECFLAGS set, the compilation fails. Using
> LDFLAGS makes the compilation process continue a little more, but it
> still doesn't solve the problem. AFAIK, the reason it doesn't solve the
> problem is, again, because we are not propagating it through the
> Makefile. Can you see any different reason? Also, should we propagate
> LDFLAGS through Makefile? IMHO, we should.

Again, if you specify CC as above, you don't have to.

> Ohh, before I forget: compilation succeeds if we use only CC='gcc -m64'.
> But again, I don't think this is a solution for this issue :-).

Why not?

Regards,
Martin