Issue 1019715: distutils ignores configure's --includedir (original) (raw)

Issue1019715

Created on 2004-08-31 14:37 by josephwinston, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg60561 - (view)	Author: Joseph Winston (josephwinston)	Date: 2004-08-31 14:37
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.
msg81098 - (view)	Author: Akira Kitada (akitada) *	Date: 2009-02-03 21:21
I'm having the same problem. This is a real headache, especially on systems that run both 32-bit and 64-bit apps, where I often see "lib64", "include64" and "bin64". In my opinion, lib, include and bin shouldn't be hard-coded in anywhere. Note that these hard-coded paths are found in other places, too. See http://bugs.python.org/issue1294959 for further detials.
msg92542 - (view)	Author: Akira Kitada (akitada) *	Date: 2009-09-12 12:46
I think this is duplicate of .
msg92608 - (view)	Author: Senthil Kumaran (orsenthil) *	Date: 2009-09-14 13:11
Yes, this is a duplicate of and tarek is assigned to that one too.