[issue858809] Use directories from configure rather than hardcoded

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 di

[issue858809] Use directories from configure rather than hardcoded

Changes by Andy Buckley : -- nosy: +andybuckley ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue858809] Use directories from configure rather than hardcoded

jan matejek 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 "prefix/lib64"

[issue858809] Use directories from configure rather than hardcoded

Martin v. Löwis 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 work". Unfortuna

[issue858809] Use directories from configure rather than hardcoded

Éric Araujo 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 supports using d

[issue858809] Use directories from configure rather than hardcoded

Éric Araujo 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 _

[issue858809] Use directories from configure rather than hardcoded

Changes by Éric Araujo : -- Removed message: http://bugs.python.org/msg45044 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue858809] Use directories from configure rather than hardcoded

Éric Araujo added the comment: About lib vs. lib64 vs. lib32, see also http://bugs.python.org/issue1294959#msg94941 -- ___ Python tracker ___ _

[issue858809] Use directories from configure rather than hardcoded

Éric Araujo added the comment: FYI, disutils is being improved as a new package named distutils2. It is not a complete redesign, but we break backward compatibility when required, so there’s hope. -- versions: +Python 3.2 -Python 2.6, Python 3.1 __

[issue858809] Use directories from configure rather than hardcoded

Changes by Éric Araujo : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/opt

[issue858809] Use directories from configure rather than hardcoded

Éric Araujo added the comment: (Fixing Roundup form bug) -- assignee: skrah -> tarek nosy: -skrah ___ Python tracker ___ ___ Python

[issue858809] Use directories from configure rather than hardcoded

Changes by Éric Araujo : -- assignee: tarek -> skrah nosy: +merwok, skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue858809] Use directories from configure rather than hardcoded

Changes by Daniel Diniz : -- 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 _

[issue858809] Use directories from configure rather than hardcoded

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

[issue858809] Use directories from configure rather than hardcoded

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. PYTHONHOME speci

[issue858809] Use directories from configure rather than hardcoded

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 after th

[issue858809] Use directories from configure rather than hardcoded

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 be the easy fi

[issue858809] Use directories from configure rather than hardcoded

jan matejek 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

[issue858809] Use directories from configure rather than hardcoded

jan matejek 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 _

[issue858809] Use directories from configure rather than hardcoded

Changes by jan matejek : -- nosy: +matejcik ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue858809] Use directories from configure rather than hardcoded

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- versions: -Python 2.5.3 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs

[issue858809] Use directories from configure rather than hardcoded

Roumen Petrov <[EMAIL PROTECTED]> added the comment: The complete patch require redesign of python-distutils ;) -- nosy: +rpetrov ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue858809] Use directories from configure rather than hardcoded

Changes by Akira Kitada <[EMAIL PROTECTED]>: -- versions: +Python 2.5.3, Python 2.6, Python 2.7, Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue858809] Use directories from configure rather than hardcoded

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]$ c

[issue858809] Use directories from configure rather than hardcoded

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 wit