STINNER Victor added the comment:
Start of this issue:
"Current Makefile.pre.in contains paths like $(exec_prefix)/lib, which bad
especially for mixed 32-bit and 64-bit systems, where 64-bit things should go
to /lib64."
That's a duplicate of bpo-1294959. This issue discuss also modifying
Changes by Andy Buckley a...@insectnation.org:
--
nosy: +andybuckley
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue858809
___
___
Python-bugs-list
jan matejek jmate...@suse.cz added the comment:
the problem this patch was solving is python libraries install into
prefix/lib regardless of what is the correct local LIBDIR - which is
obviously broken on systems where LIBDIR is something other than prefix/lib,
most notable example being
Éric Araujo mer...@netwok.org added the comment:
About lib vs. lib64 vs. lib32, see also
http://bugs.python.org/issue1294959#msg94941
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue858809
Changes by Éric Araujo mer...@netwok.org:
--
Removed message: http://bugs.python.org/msg45044
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue858809
___
Éric Araujo mer...@netwok.org added the comment:
I don’t know much about Makefile.pre.in, so I can’t say anything about the
patch. Martin, could you maybe comment?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
Éric Araujo mer...@netwok.org added the comment:
From http://bugs.python.org/issue1294959#msg94986
“The main problem is that Python's configuration system is not
geared up to having the lib directories for platform dependent
and platform independent parts use different names.
It currently only
Martin v. Löwis mar...@v.loewis.de added the comment:
I don't think anything in distutils can solve whatever the problem is that
people perceive.
All I can say about the patch is that it apparently doesn't do any harm. I
expect that, if it is accepted, people continue complain that it doesn't
Changes by Éric Araujo mer...@netwok.org:
--
assignee: tarek - skrah
nosy: +merwok, skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue858809
___
Éric Araujo mer...@netwok.org added the comment:
(Fixing Roundup form bug)
--
assignee: skrah - tarek
nosy: -skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue858809
___
Changes by Éric Araujo mer...@netwok.org:
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue858809
___
___
Python-bugs-list mailing list
Changes by Daniel Diniz aja...@gmail.com:
--
assignee: - tarek
components: +Distutils
nosy: +tarek
stage: - needs patch
type: - behavior
versions: +Python 3.1 -Python 2.5, Python 2.7, Python 3.0
___
Python tracker rep...@bugs.python.org
soundmurderer soundmurde...@gmail.com 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
soundmurderer soundmurde...@gmail.com 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
soundmurderer soundmurde...@gmail.com 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!
soundmurderer soundmurde...@gmail.com 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
Changes by jan matejek jmate...@suse.cz:
--
nosy: +matejcik
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue858809
___
___
Python-bugs-list mailing
jan matejek jmate...@suse.cz added the comment:
well, seeing as redesign of distutils probably won't happen anytime soon...
why don't we fix the obvious bug (broken configure) now and redesign
distutils later?
___
Python tracker rep...@bugs.python.org
jan matejek jmate...@suse.cz added the comment:
...the patch is absolutely trivial, doesn't have any deep consequences
and applies cleanly to head and all branches i know of.
...i wonder if the patch-fasttracking offer still applies...
___
Python tracker
Changes by Martin v. Löwis [EMAIL PROTECTED]:
--
versions: -Python 2.5.3
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue858809
___
___
Python-bugs-list
Changes by Akira Kitada [EMAIL PROTECTED]:
--
versions: +Python 2.5.3, Python 2.6, Python 2.7, Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue858809
___
Roumen Petrov [EMAIL PROTECTED] added the comment:
The complete patch require redesign of python-distutils ;)
--
nosy: +rpetrov
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue858809
___
Joseph Rothrock [EMAIL PROTECTED] added the comment:
Hi,
This problem still exists in 2.5.2. Setting the libdir argument doesn't
correctly set LIBDIR in the Makefile.
[EMAIL PROTECTED] Python-2.5.2]$ ./configure --prefix=/home/y
--libdir=/home/y/lib64
...
[EMAIL PROTECTED] Python-2.5.2]$
Sérgio Durigan Júnior [EMAIL PROTECTED] added the comment:
Hi,
Continuing with my effort to improve Python's build system, I'd really
like to know why this issue has not been solved yet. I mean, apparently
this problem is still present in Python 2.5, since I can't change the
library's path with
24 matches
Mail list logo
