[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

STINNER Victor added the comment: I mark this issue as a duplicate of bpo-1294959. -- nosy: +vstinner resolution: out of date -> duplicate superseder: -> Problems with /usr/lib64 builds. ___ Python tracker

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Change by Matej Cepl : -- nosy: +mcepl ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Colin McCabe added the comment: When installing Python 3.6.3 from source on openSUSE Leap 42.2, this bug still occurs. Python cannot find the readline module, until you symlink $prefix/lib/python3.6/lib-dynload to $prefix/lib64/python3.6/lib-dynload. -- nosy:

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Skip Montanaro added the comment: Not relevant to me. On Sep 8, 2016 5:45 PM, "Christian Heimes" wrote: > > Christian Heimes added the comment: > > Can we close the ticket or is it still relevant? > > -- > nosy: +christian.heimes > status: open -> pending > >

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Changes by Christian Heimes : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Christian Heimes added the comment: Can we close the ticket or is it still relevant? -- nosy: +christian.heimes status: open -> pending ___ Python tracker

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Catalin Iacob added the comment: In reply to msg168184, LIBDIR is set to include lib64 instead of lib because openSUSE explicitly does it that way in their multilib implementation. More specifically, the CONFIG_SITE environment variable is set to /usr/share/site/x86_64-unknown-linux-gnu which

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Roumen Petrov added the comment: Skip, You mix two technologies one is --libdir that could be specified at configure time and another one is sub-directory name for libraries as path suffix to some prefixes. You could just adjust python to use user specified path (--libdir) and this is more

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Roumen Petrov added the comment: Also I could not understand why is opened new issue. Just search for libdir and one is Issue 1294959 - 7 years old with the same idea. Later mean that solution is not acceptable. -- ___ Python tracker

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Skip Montanaro added the comment: Before this goes any farther, let me make this clear - I *did not* develop this patch. It was developed by the OpenSUSE folks. I had trouble installing Python from source on the OpenSUSE system under my desk at work. I asked about the problem on

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Matthias Klose added the comment: the proposed patch has still some issues: - it breaks the installation on 64bit platforms on Debian and Ubuntu. Please test the patch on one of these platforms too. - it hardcodes more platform information in the sys modules, which makes it difficult

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Skip Montanaro added the comment: the proposed patch has still some issues: - it breaks the installation on 64bit platforms on Debian and Ubuntu. Please test the patch on one of these platforms too. - it hardcodes more platform information in the sys modules, which makes it

[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

Skip Montanaro added the comment: I applied the OpenSUSE patch to the current cpython tip (3.4a0), rebuilt, then reinstalled. I verified that sys.path contains directories which contain lib64. I can import the time module now, which failed before applying the patch. The patch didn't apply