Build Python2.4.1 on AIX5 using xlc v6

[npkg]

BPO	1209781
Nosy	@loewis, @birkenfeld
Files	AIX-Python241-diff.txt: Patch to get Python-2.4.1 to compile on AIX using IBM's xlc

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2006-02-19.15:29:19.000>
created_at = <Date 2005-05-27.11:53:36.000>
labels = ['build']
title = 'Build Python2.4.1 on AIX5 using xlc v6'
updated_at = <Date 2006-02-19.15:29:19.000>
user = 'https://bugs.python.org/npkg'

bugs.python.org fields:

activity = <Date 2006-02-19.15:29:19.000>
actor = 'georg.brandl'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Build']
creation = <Date 2005-05-27.11:53:36.000>
creator = 'npkg'
dependencies = []
files = ['6671']
hgrepos = []
issue_num = 1209781
keywords = ['patch']
message_count = 4.0
messages = ['48388', '48389', '48390', '48391']
nosy_count = 3.0
nosy_names = ['loewis', 'georg.brandl', 'npkg']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1209781'
versions = ['Python 2.4']

[npkg]

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.

[loewis]

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?

[npkg]

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.

[birkenfeld]

Logged In: YES
user_id=1188172

Most of this was already done by Guido's AIX patches. I
removed only the trailing commas in rev. 42498.