Message 162230 - Python tracker

➜

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.

In-reply-to
Author	ndparker
Recipients	ndparker
Date	2012年06月03日.19:31:08
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1338751869.08.0.200680664927.issue14994@psf.upfronthosting.co.za>

Content
GCC error when using pyerrors.h This ist my first attempt to test an extension with python 3.3. I've been using the 3.3.0a4 tarball. I'm using very strict compiler settings when compiling my extension modules, especially -Wall -Werror (along with a lot more flags, like -pedantic, -std=c89). Including Python.h includes pyerrors.h which emits: /usr/include/python3.3/pyerrors.h:91:8: error: "__GNUC_MAJOR__" is not defined /usr/include/python3.3/pyerrors.h:92:8: error: "__GNUC_MAJOR__" is not defined I'm not sure, which of the compiler flags is responsible for dropping those macros. Simple defined() checks should fix that problem though.

Content

GCC error when using pyerrors.h
This ist my first attempt to test an extension with python 3.3. I've been using the 3.3.0a4 tarball.
I'm using very strict compiler settings when compiling my extension modules, especially -Wall -Werror (along with a lot more flags, like -pedantic, -std=c89).
Including Python.h includes pyerrors.h which emits:
/usr/include/python3.3/pyerrors.h:91:8: error: "__GNUC_MAJOR__" is not defined
/usr/include/python3.3/pyerrors.h:92:8: error: "__GNUC_MAJOR__" is not defined
I'm not sure, which of the compiler flags is responsible for dropping those macros. Simple defined() checks should fix that problem though.

History
Date	User	Action	Args
2012年06月03日 19:31:09	ndparker	set	recipients: + ndparker
2012年06月03日 19:31:09	ndparker	set	messageid: <1338751869.08.0.200680664927.issue14994@psf.upfronthosting.co.za>
2012年06月03日 19:31:08	ndparker	link	issue14994 messages
2012年06月03日 19:31:08	ndparker	create

homepage