[issue896330] pyconfig.h is not placed in --includedir

[Ned Deily]

Change by Ned Deily :


--
nosy:  -Mario Gonzalez

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Ned Deily]

Change by Ned Deily :


--
Removed message: https://bugs.python.org/msg372730

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Mario Gonzalez]

Mario Gonzalez  added the comment:

hey u, send mi a mail, u need my help
and i need u 
mario the last one
mario.cro...@gmail.com

--
nosy: +Mario Gonzalez

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Lauri Tirkkonen]

Lauri Tirkkonen added the comment:

Patch attached to set CONFINCLUDEDIR to --includedir. There's additionally some 
hardcoded assumptions in sysconfig and distutils.sysconfig about the include 
paths, of which this patch fixes some.

What it doesn't address is sysconfig.get_path with 'include' or 'platinclude'. 
There 'include', however, were already broken if python was configured with 
--includedir ('platinclude' was correct because it was hardcoded, and 
pyconfig.h always installed to the same place). I think those should also be 
fixable by getting the correct directories from _sysconfigdata instead of 
hardcoding possible 'installation schemes' and trying some de-facto paths based 
on those. I suspect this is also a problem for library paths, but this issue is 
only concerned with includedir.

I suspect the problem that 'CONFINCLUDEDIR' was trying to solve is separating 
platform-dependent headers from platform-independent ones, but it doesn't 
actually solve that problem correctly: pyconfig.h does not go in --includedir 
AND the hardcoded include path for pyconfig.h doesn't go in python-config 
--includes output.

--
keywords: +patch
nosy: +lotheac
Added file: http://bugs.python.org/file36552/pyconfig-includedir.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue896330
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Mark Lawrence]

Changes by Mark Lawrence breamore...@yahoo.co.uk:


--
nosy:  -BreamoreBoy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue896330
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Christian Heimes]

Christian Heimes added the comment:

I found the reason for the issue. pyconfig.h is installed to CONFINCLUDEPY. The 
other header files are copied to INCLUDEPY

INCLUDEDIR= @includedir@
CONFINCLUDEDIR= $(exec_prefix)/include

INCLUDEPY=  $(INCLUDEDIR)/python$(LDVERSION)
CONFINCLUDEPY=  $(CONFINCLUDEDIR)/python$(LDVERSION)


@for i in $(srcdir)/Include/*.h; \
do \
echo $(INSTALL_DATA) $$i $(INCLUDEPY); \
$(INSTALL_DATA) $$i $(DESTDIR)$(INCLUDEPY); \
done
$(INSTALL_DATA) pyconfig.h $(DESTDIR)$(CONFINCLUDEPY)/pyconfig.h

--
stage:  - needs patch
versions: +Python 3.3, Python 3.4, Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue896330
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Göran Uddeborg]

Göran Uddeborg goe...@uddeborg.se added the comment:

I tried by building Python 3.1.2 with the configuration

... --prefix=$home/ptest --includedir=$home/ptest/myspecialincludedir

pyconfig.h still wound up in $prefix/include/python3.1, while all other header 
files were correctly placed in $prefix/myspecialincludedir/python3.1.

So yes, it is still a problem.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue896330
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Mark Lawrence]

Mark Lawrence breamore...@yahoo.co.uk added the comment:

Is this still a problem, sorry I don't have a box to test it on?

--
nosy: +BreamoreBoy
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6, Python 3.0

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue896330
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Daniel Diniz]

Changes by Daniel Diniz aja...@gmail.com:


--
type:  - behavior

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue896330
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue896330] pyconfig.h is not placed in --includedir

[Christian Heimes]

Christian Heimes added the comment:

I'm able to reproduce the bug with 2.6

--
nosy: +tiran
priority: normal - low
severity: normal - minor
versions: +Python 2.6, Python 3.0 -Python 2.2


Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue896330

___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com