[Patches] [ python-Patches-1209781 ] Build Python2.4.1 on AIX5 using xlc v6

[SourceForge.net]

Patches item #1209781, was opened at 2005-05-27 11:53
Message generated for change (Comment added) made by npkg
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1209781&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Gangadhar NPK (npkg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Build Python2.4.1 on AIX5 using xlc v6

Initial Comment:
Using IBM's Visualage compiler to build Python on AIX,
requires small changes to the code, to let it compile
cleanly.
OS version: AIX 5.2
xlc version: 6

The changes are:
1 AIX defines hz as a preprocessor symbol and it
creates a conflict during preprocessing in the
_codecs_cn.c. This symbol has been selectively
undefined for AIX only
2.Trailing commas in an enum
3. Multiple defines of the _THREAD_SAFE symbol in
python/thread.c. This has been selectively undefined.



----------------------------------------------------------------------

>Comment By: Gangadhar NPK (npkg)
Date: 2005-06-16 17:41

Message:
Logged In: YES 
user_id=587037

Sorry for not responding, was a little busy. I will check
the last one - could be because of the patch levels too.
Will check and post it here.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2005-05-30 08:25

Message:
Logged In: YES 
user_id=21627

These patches look fine except for the last chunk. I very
much doubt that xlc cannot handle multiple defines; ISO C
mandates that a redefine is allowed as long as the
replacement lists of the macros are identical (6.10.3p2). So
if xlc complains, it is likely that it has a different
definition than the one it reports a conflict is.

Also, it is unclear what precisely the conflict is: AFAICT,
Python never defines _THREAD_SAFE itself. So the conflict
must be between two AIX header files.

Can you please investigate this aspect further?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1209781&group_id=5470