Issue896330
Created on 2004-02-13 08:24 by goeran, last changed 2008-01-03 23:33 by christian.heimes.
| msg19983 (view) |
Author: Göran Uddeborg (goeran) |
Date: 2004-02-13 08:24 |
|
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.
|
| msg19984 (view) |
Author: Pelle Johansson (morth) |
Date: 2004-10-23 13:52 |
|
Logged In: YES
user_id=180081
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.
|
| msg19985 (view) |
Author: Martin v. Löwis (loewis) |
Date: 2006-04-12 08:05 |
|
Logged In: YES
user_id=21627
I don't think I will do anything about this anytime soon, so
unassigning myself.
|
| msg59177 (view) |
Author: Christian Heimes (christian.heimes) |
Date: 2008-01-03 23:33 |
|
I'm able to reproduce the bug with 2.6
|
|
| Date |
User |
Action |
Args |
| 2008-01-03 23:33:54 | christian.heimes | set | priority: normal -> low nosy:
+ christian.heimes messages:
+ msg59177 severity: normal -> minor versions:
+ Python 2.6, Python 3.0, - Python 2.2 |
| 2004-02-13 08:24:58 | goeran | create | |
|