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 thomas.perl
Recipients Alex.Willmer, martin.panter, thomas.perl, xdegaye
Date 2016-07-13.15:30:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Adding "-mfloat-abi=hard" to LDFLAGS fixes the issue for me, and also allows $(BUILDPYTHON) to be built correctly in addition to $(PGEN).

So I guess the resolution to this issue is "works for me" (with setting CC or LDFLAGS properly for cross-compilation being the resolution/workaround).

Does it make sense to create a new bug "Do not build pgen when it's not going to be used" as follow-up to this discussion (with a patch similar to the one in If so, I'll create one. Or maybe there should be a generic configure flag "do not run any generators" (like, but including not running pgen), with the flag only issuing warnings instead of failing.
Date User Action Args
2016-07-13 15:30:32thomas.perlsetrecipients: + thomas.perl, xdegaye, martin.panter, Alex.Willmer
2016-07-13 15:30:31thomas.perlsetmessageid: <>
2016-07-13 15:30:31thomas.perllinkissue27490 messages
2016-07-13 15:30:31thomas.perlcreate