[issue5404] Cross-compiling Python

Martin Panter added the comment: Wilcox: 3.4 is in security maintainence mode. I suggest using 3.5, or look at backporting revision d00837de03d7 (Issue 26884), which I presume fixes this. -- nosy: +martin.panter ___ Python tracker

[issue5404] Cross-compiling Python

awilfox added the comment: Bootstrapping a Linux environment based on musl libc from glibc host requires cross-compilation to the same architecture (for example, configure is --build=i686-pc-linux-gnu --host=i686-pc-linux-musl). The Python core will build and link fine in this configuration; u

[issue5404] Cross-compiling Python

Changes by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue5404] Cross-compiling Python

Stefan Krah added the comment: Here's a cross-compile script for arm-linux-gnueabi. Building 3.4 works on Ubuntu 14.04. I cannot run the tests, since I only have an old Debian-ARM qemu image with the wrong glibc version. For 3.5 we have a regression due to the new matrix operator. -- A

[issue5404] Cross-compiling Python

Gregory P. Smith added the comment: I haven't tried a cross compile in ages. If nothing else I don't think this issue should be closed until we have at least one buildbot setup to cross compile it and run it on the target platform. That's on my long "todo for python" wish list but I haven't h

[issue5404] Cross-compiling Python

Stefan Krah added the comment: Ping. Is this still an issue for anyone in 3.4? -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue5404] Cross-compiling Python

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue5404] Cross-compiling Python

Stefan Krah added the comment: Cross compiling for arm works here on Ubuntu: $ cat config.site ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no $ export CONFIG_SITE=$PWD/config.site $ ./configure --host=arm-linux-gnueabi --build=x86_64 --disable-ipv6 $ make I cannot test though, since I don't

[issue5404] Cross-compiling Python

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue5404] Cross-compiling Python

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue5404] Cross-compiling Python

Changes by Guido van Rossum : -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue5404] Cross-compiling Python

Mark Lawrence added the comment: I understand that cross-compilation is not supported so this must now be aimed at 3.2. -- nosy: +BreamoreBoy versions: +Python 3.2 -Python 2.5 ___ Python tracker __

[issue5404] Cross-compiling Python

Changes by Gregory P. Smith : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue5404] Cross-compiling Python

Joshua Kinard added the comment: Roumen, I took a look at 4010, and tried your patch (as well as attempted to apply the latter patch, but they changes are too great). Neither one helped resolve my issue, but I should probably explain the angle I'm attacking this from so you have an idea of wha

[issue5404] Cross-compiling Python

Roumen Petrov added the comment: Joshua, may be you need patch from Issue4010 to pass LDFLAGS to distutils. Another issue4305 - it is for mipsel. About cross compilation - yes it is Python flaw. For past ten years the progress is near to zero. About you problem - #error "LONG_BIT definition ap

[issue5404] Cross-compiling Python

Changes by Antoine Pitrou : -- nosy: +tarek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue5404] Cross-compiling Python

Joshua Kinard added the comment: Making progress! Adapted the cross-2.5.1.patch from Issue #1597850, integrated the %zd printf fixup patch, and added another cross-compiler check for the libffi configure bits in setup.py (it'd pass libffi's configure no --host options, so libffi would compile f

[issue5404] Cross-compiling Python

Martin v. Löwis added the comment: > Do you guys maintain any kind of an "internals" guide to the build > system anywhere? Like an outline or such of what happens from start to > finish when you run setup.py (I think that's the start, anyways)? Besides the code, and besides the very high-level

[issue5404] Cross-compiling Python

Joshua Kinard added the comment: Gotcha. Not sure how far off Gentoo is from supporting 2.6 -- our primary package manager relies on it, so the updates tend to be slow. for moving to new versions. Do you guys maintain any kind of an "internals" guide to the build system anywhere? Like an outl

[issue5404] Cross-compiling Python

Martin v. Löwis added the comment: > Gotcha, I'll poke around and see what I can find. Are you guys open to > patches for 2.5.x still if we find something that needs patching (versus > passing lots of variables to the make process)? No. The Python 2.5 branch is closed; the 2.6 branch doesn't a

[issue5404] Cross-compiling Python

Joshua Kinard added the comment: Gotcha, I'll poke around and see what I can find. Are you guys open to patches for 2.5.x still if we find something that needs patching (versus passing lots of variables to the make process)? ___ Python tracker

[issue5404] Cross-compiling Python

Changes by Roumen Petrov : -- nosy: +rpetrov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue5404] Cross-compiling Python

Martin v. Löwis added the comment: In short: cross-compilation is not supported at all, and it will be very very difficult to implement. Search this tracker for proposed solutions, and comment in each proposed solution whether it would help in your case. -- nosy: +loewis __

[issue5404] Cross-compiling Python

New submission from Joshua Kinard : I'm attempting to get Python to cross-compile, and I'm not sure if this is an actual flaw in the build system or not, but thought I'd detail what I can here and seek comment from those in the know. What happens is under a cross-environment setup on a Gentoo in