This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Trevor.Bowen, r.david.murray
Date 2013-10-02.13:04:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380719054.01.0.846015208557.issue19142@psf.upfronthosting.co.za>
In-reply-to
Content
I have no idea, frankly :)

I guess my point is that the tool chain was not designed with cross compilation in mind, so sorting out how to make it work and writing a howto is something that needs to be done.  The patches that have already been applied address a narrow need felt and fixed by the Debian folk, dealing with cross compiling 64 bit vs 32 bit, if I understand correctly.  I don't know if it is a general cross compile fix, but in theory it should at least have moved us closer.

Now, that said, as far as build order goes, what we do in general is to check in the sources that are built by the tools.  If you get your sources out of a tarball, make shouldn't try to rebuild those.  If you are working from a checkout, try 'make touch' before the make, to update the timestamps the way they would be in a release tarball.
History
Date User Action Args
2013-10-02 13:04:14r.david.murraysetrecipients: + r.david.murray, Trevor.Bowen
2013-10-02 13:04:14r.david.murraysetmessageid: <1380719054.01.0.846015208557.issue19142@psf.upfronthosting.co.za>
2013-10-02 13:04:13r.david.murraylinkissue19142 messages
2013-10-02 13:04:13r.david.murraycreate