[Python-Dev] Naming of config.h

Martin v. Loewis martin@loewis.home.cs.tu-berlin.de
Thu, 7 Sep 2000 22:26:28 +0200

The fact that Python installs its config.h as
<prefix>/python2.0/config.h is annoying if one tries to combine Python
with some other autoconfiscated package.

If you configure that other package, it detects that it needs to add
-I/usr/local/include/python2.0; it also provides its own
config.h. When compiling the files

#include "config.h"

could then mean either one or the other. That can cause quite some
confusion: if the one of the package is used, LONG_LONG might not
exist, even though it should on that port.

This issue can be relaxed by renaming the "config.h" to
"pyconfig.h". That still might result in duplicate defines, but likely
SIZE_FLOAT (for example) has the same value in all definitions.