[ python-Bugs-896330 ] pyconfig.h is not placed in --includedir

SourceForge.net noreply at sourceforge.net
Wed Apr 12 10:05:28 CEST 2006

Bugs item #896330, was opened at 2004-02-13 09:24
Message generated for change (Comment added) made by loewis
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: Python 2.2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Göran Uddeborg (goeran)
>Assigned to: Nobody/Anonymous (nobody)
Summary: pyconfig.h is not placed in --includedir

Initial Comment:
When configuring Python with an explicit --includedir
most of the header files do turn up in this directory.
 But the pyconfig.h is still placed in $(prefix)/include.

I assume it is a bug, and this file too should be
placed according to --includedir.


>Comment By: Martin v. Löwis (loewis)
Date: 2006-04-12 10:05

Logged In: YES 

I don't think I will do anything about this anytime soon, so
unassigning myself.


Comment By: Pelle Johansson (morth)
Date: 2004-10-23 15:52

Logged In: YES 

Actually, pyconfig.h is placed in $(exec-prefix)/include.
This is fine as the file is architecture dependant.
However the other header files use a local
#include "pyconfig.h"
which will not match if it's not the same dir. If you like
me want a common directory for all archindependant files and
then separate for each arch it causes additional headache,
since there's no easy way for me to symlink from the arch
include/ dir to the archindependant, as they have a common
subdir (python2.3/ in my case).

Currently it seems I'll have to symlink each header file
individually from the archindependent dir to the arch ones.
Ideally pyconfig.h would be put directly in
$(exec-prefix)/include/ and be refered to as <pyconfig.h>. I
could then just symlink the subdir.

Whether to honor includedir or not I don't know, I'll leave
that problem to the project.


You can respond by visiting: 

More information about the Python-bugs-list mailing list