soundmurderer added the comment:
I can confirm that --bindir and --libdir are broken in Python 2.6.2,
despite the fact that ./configure --help lists them as helpful options.
At the very least, ./configure should complain if you're using options
that don't do anything! That would b
soundmurderer added the comment:
I tried applying nijel's 2.3.2 patch to Python 2.6.2 Makefile.pre.in,
then configure/make/install with --bindir and --libdir flags to
./configure. It works in terms of producing the correct Makefile with
LIBDIR and BINDIR that I want, but I get problems
soundmurderer added the comment:
OK, I am now convinced that even with this patch, the Python build
process still won't work correctly because --libdir (post-patch) will
not correctly set the default PYTHONHOME. Moreover, the very way that
PYTHONHOME gets used needs to change. PYTHO
New submission from soundmurderer :
The PYTHONHOME variable does not allow complete control over making a
Python installation find its own libs because "lib/pythonX.Y" gets
appended to it, see:
http://docs.python.org/using/cmdline.html#envvar-PYTHONHOME
For example, let'
soundmurderer added the comment:
OK done, opened a feature request for this pet peeve of mine. ;-) Maybe
someday I'll complain about something substantial...
See: http://bugs.python.org/issue6060
--
___
Python tracker
<http://bugs.py
soundmurderer added the comment:
OK, I'm convinced. Changing PYTHONHOME is bad. But I am all in favor
R. David Murray's solution of extending to include something like
PYTHONHOMELIB.
Martin v. Löwis: What I want is simply to be able to use --libdir to
tell ./configure where to pu
