[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

R. David Murray added the comment: Sure. It can always be reopened if the OP comes back and says it isn't fixed. I'm closing it out of date because there are no references to checkins that fixed it. -- nosy: +r.david.murray resolution: -> out of date stage: -> committed/rejected s

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Terry J. Reedy added the comment: In the absence of further complaints, this appears to really be fixed. Should it be closed as such? -- nosy: +tjreedy status: pending -> open ___ Python tracker __

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Antoine Pitrou added the comment: It seems everything has been fixed in the 2.6 branch and in trunk. Andrew, can you do a quick SVN checkout and test it? -- nosy: +pitrou ___ Python tracker

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Andrew Paprocki <[EMAIL PROTECTED]> added the comment: The list of files/lines I posted yesterday was all that I had to change to get it to build here (where a C++ style comment is a syntax error), so it doesn't seem like a massive change. ___ Python tracker <

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: On 2008-12-03 01:44, Christian Heimes wrote: > Christian Heimes <[EMAIL PROTECTED]> added the comment: > > Barry, the issue in _ctypes/callproc.c could be a problem for us > although Python 2.6 and 3.0 are compiling fine with -std=c89. Sh

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: For 2.6.1, yes you can fix the comments if you can do it now :) ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Christian Heimes <[EMAIL PROTECTED]> added the comment: Barry, the issue in _ctypes/callproc.c could be a problem for us although Python 2.6 and 3.0 are compiling fine with -std=c89. Should the comment be fixed before the release? -- assignee: christian.heimes -> barry nosy: +barry resol

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: There are still quite a few C99 comments left in the code, esp. in code that's meant for MSVC (which works fine with them) and code for the Mac (which uses gcc and also doesn't have problems with them). Esp. the ctypes and libffi code is f

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Andrew Paprocki <[EMAIL PROTECTED]> added the comment: summary of compiler errors/warnings i just hit in the same situation with stock Python-2.6.tgz: >> c++ style comment used "Objects/frameobject.c", line 520.9: 1506-046 (S) Syntax error. "Objects/unicodeobject.c", line 118.1: 1506

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Georg Brandl <[EMAIL PROTECTED]> added the comment: Christian, I guess it's all fixed now? -- assignee: -> christian.heimes nosy: +christian.heimes, georg.brandl resolution: -> fixed status: open -> pending ___ Python tracker <[EMAIL PROTECTED]>

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

New submission from David Jones <[EMAIL PROTECTED]>: Doing a plan "configure" then "make"; the compilation breaks due to // style comments in a file called Objects/frameobject.c: cc_r -qlanglvl=extc89 -c -DNDEBUG -O -I. -IInclude -I./Include - DPy_BUILD_CORE -o Objects/frameobject.o Objects