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 eric.araujo
Recipients Seppo.Yli-Olli, alexis, eric.araujo, jonforums, loewis, rpetrov, rubenvb, santoso.wijaya, schmir, tarek
Date 2011-10-27.16:03:55
SpamBayes Score 4.5133913e-08
Marked as misclassified No
Message-id <>
> Would it be practical to have a trivial compilation test to see if we
> are capable of using GCC with -mno-cygwin and if so, use it, otherwise
> drop off? I think GNU autotools uses a similar strategy for detecting
> compiler capabilities.

The config command does such things, but the compiler classes don’t.  I’d prefer something more lightweight, like a version check (see msg141231).
Date User Action Args
2011-10-27 16:03:56eric.araujosetrecipients: + eric.araujo, loewis, schmir, tarek, rpetrov, rubenvb, santoso.wijaya, alexis, Seppo.Yli-Olli, jonforums
2011-10-27 16:03:56eric.araujosetmessageid: <>
2011-10-27 16:03:56eric.araujolinkissue12641 messages
2011-10-27 16:03:55eric.araujocreate