Supressing warnings with -w "whether gcc supports ParseTuple"

[samueljohn]

BPO	15127
Nosy	@serhiy-storchaka

^{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 2018-07-23.20:01:04.188>
created_at = <Date 2012-06-21.17:02:57.020>
labels = ['build']
title = 'Supressing warnings with -w  "whether gcc supports ParseTuple"'
updated_at = <Date 2018-07-23.20:01:04.186>
user = 'https://bugs.python.org/samueljohn'

bugs.python.org fields:

activity = <Date 2018-07-23.20:01:04.186>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = True
closed_date = <Date 2018-07-23.20:01:04.188>
closer = 'serhiy.storchaka'
components = ['Build']
creation = <Date 2012-06-21.17:02:57.020>
creator = 'samueljohn'
dependencies = []
files = []
hgrepos = []
issue_num = 15127
keywords = []
message_count = 3.0
messages = ['163349', '222689', '322250']
nosy_count = 3.0
nosy_names = ['samueljohn', 'BreamoreBoy', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue15127'
versions = ['Python 3.2']

[samueljohn]

In configrue.in, Python checks if the compiler supports __attribute__((format(PyArg_ParseTuple, 2, 3))) and sets the CFLAGS to "CFLAGS -Werror" to decide this test.

When you build Python with "CFLAGS=-w" (homebrew's default), configure reports

whether gcc supports ParseTuple ... yes

which is not supported for clang (I was told).

I know it's hard to remove a certain flag from the CFLAGS, but perhaps there should be better documentation about this issue.

[BreamoreBoy]

@samuel sorry about the delay in getting back to you :(

Can we have a comment on this please.

[serhiy-storchaka]

This code was removed in f6b687f.