Author martin.panter
Recipients Alex.Willmer, martin.panter, xdegaye
Date 2016-10-29.03:26:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477711568.13.0.876919775631.issue28542@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks, this looks like a decent start. I’m not that familiar with cross-compiling Python, but here are a couple questions:

$(cd /path/to/source && pwd)/configure
Why do you use $(pwd) here? I have mainly seen relative paths used (my own experiments, and reports from others), so I don’t think you need to force an absolute path. The instructions further up already mention “../configure” from a subdirectory.

--prefix=$(cd ../install && pwd)
Won’t that embed the path of the install directory in e.g. sys.prefix or something? Can’t you use “DESTDIR=../install” instead?

I remember there are a bunch of extra things you have to manually configure to cross-compile. See e.g. revision 12a56a349af2 which asks for /dev/ptmx and /dev/ptc settings in a CONFIG_SITE file (although I have had success just adding them to the “configure” command line). Perhaps we could add something like

'''
configure --host=[. . .] \
    ac_cv_file__dev_ptmx=no \
    ac_cv_file__dev_ptc=no
. . .

If the target Python could use /dev/ptmx or /dev/ptc to implement os.openpty(), set the corresponding argument to "yes".
'''

I suspect some people cross compile 2.7, so it may be worth applying something like this to that branch.
History
Date User Action Args
2016-10-29 03:26:08martin.pantersetrecipients: + martin.panter, xdegaye, Alex.Willmer
2016-10-29 03:26:08martin.pantersetmessageid: <1477711568.13.0.876919775631.issue28542@psf.upfronthosting.co.za>
2016-10-29 03:26:08martin.panterlinkissue28542 messages
2016-10-29 03:26:07martin.pantercreate