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 pitrou
Recipients drj, jabt, nnorwitz, pitrou, sable, smudd
Date 2010-09-14.10:12:34
SpamBayes Score 7.472216e-09
Marked as misclassified No
Message-id <1284459156.75.0.453774182963.issue1633863@psf.upfronthosting.co.za>
In-reply-to
Content
> cc_r does not seems to be able to compile py3k, so it seems to be a bad 
> idea to force it by default.

Python should be able to compile with any C89-compliant compiler, so it seems a good idea to open a bug for compile errors instead.
In this case, the fix is trivial, though, so I'm simply committing it (replace a C++-style comment ("// ...") with a normal "/* ... */")). Can you try again with r84799?

That said, it seems xlc (or xlc_r) enables additional C extensions compared to cc, so perhaps it's beneficial to use it anyway?
History
Date User Action Args
2010-09-14 10:12:36pitrousetrecipients: + pitrou, nnorwitz, sable, jabt, smudd, drj
2010-09-14 10:12:36pitrousetmessageid: <1284459156.75.0.453774182963.issue1633863@psf.upfronthosting.co.za>
2010-09-14 10:12:35pitroulinkissue1633863 messages
2010-09-14 10:12:34pitroucreate