[Python-bugs-list] [Bug #131774] Architecture-specific config.h is badly named
noreply@sourceforge.net
noreply@sourceforge.net
Fri, 09 Feb 2001 14:10:20 -0800
Bug #131774, was updated on 2001-Feb-09 13:57
Here is a current snapshot of the bug.
Project: Python
Category: Build
Status: Open
Resolution: None
Bug Group: Feature Request
Priority: 5
Submitted by: gramirez
Assigned to : nobody
Summary: Architecture-specific config.h is badly named
Details: If Python is installed with architecture-dependent and
architecture-independent files in separate locations (using --prefix and
--exec-prefix), then config.h is placed in a directory different than
Python.h (and pyport.h and pgenheaders.h, which also #include
"config.h").
If I build a python module which has its own config.h (like pygtk), the
build fails because Python.h #include's the *wrong* config.h. I cannot
easily change the order of the
-I flags when compiling pygtk because autoconf places its flags
(AM_CPPFLAGS) before any CPPFLAGS that I define in the CPPFLAGS environment
variable.
It would be cleaner to follow the glib model which names its installed
arch-specific file "glibconfig.h". We could install config.h as
pythonconfig.h, and have Python.h #include "pythonconfig.h"
Follow-Ups:
Date: 2001-Feb-09 14:10
By: gvanrossum
Comment:
Good idea! Patch anybody?
-------------------------------------------------------
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=131774&group_id=5470