Message 60561 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Recipients
Author	josephwinston
Date	2004年08月31日.14:37:25
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
1. configure and build python using the --includedir option. For example: $ configure --prefix=/TANGO/3/rel --includedir=/TANGO/3/rel/inc 2. Run $ make install 3. Notice that the include files are placed in /TANGO/3/rel/include not /TANGO/3/rel/inc. 4. Verify with $ python -c 'from distutils.sysconfig import *;print get_python_inc() 5. The problem is that get_python_inc() hard codes the include file path to use the name "include" 6. Other programs using distutils will fail since the INSTALL_SCHEMES found in install.py also have the name "include" hard coded. 7. Suggested fix would be to use --includedir to calculate the include path used by distutils.

Content

1. configure and build python using the --includedir
option. For example:
$ configure --prefix=/TANGO/3/rel
--includedir=/TANGO/3/rel/inc
2. Run
$ make install
3. Notice that the include files are placed in
/TANGO/3/rel/include not /TANGO/3/rel/inc.
4. Verify with
$ python -c 'from distutils.sysconfig import *;print
get_python_inc()
5. The problem is that get_python_inc() hard codes the
include file path to use the name "include"
6. Other programs using distutils will fail since the
INSTALL_SCHEMES found in install.py also have the name
"include" hard coded.
7. Suggested fix would be to use --includedir to
calculate the include path used by distutils.

History
Date	User	Action	Args
2008年01月20日 09:57:08	admin	link	issue1019715 messages
2008年01月20日 09:57:08	admin	create

homepage