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

[STINNER Victor]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Matej Cepl]

Change by Matej Cepl :


--
nosy: +mcepl

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Colin McCabe]

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: +cmccabe
versions: +Python 3.6 -Python 3.3, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Skip Montanaro]

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
>
> ___
> Python tracker 
> 
> ___
>

--
status: pending -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Christian Heimes]

Changes by Christian Heimes :


--
resolution:  -> out of date
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Christian Heimes]

Christian Heimes added the comment:

Can we close the ticket or is it still relevant?

--
nosy: +christian.heimes
status: open -> pending

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Catalin Iacob]

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 contains, among more stuff:

catalin@opensuse:~/hacking/cpython cat $CONFIG_SITE  | grep libdir
# If user did not specify libdir, guess the correct target:
if test $libdir = '${exec_prefix}/lib' ; then
libdir='${exec_prefix}/lib64'


/usr/share/site/x86_64-unknown-linux-gnu is owned by package site-config whose 
README says:

site-config: Site Paths Configuration for autoconf Based configure Scripts
==

Site configuration for autoconf based configure scripts provides smart
defaults for paths that are not specified.

All autoconf based configure scripts will automatically resource site
script using CONFIG_SITE environment variable. It works without any
explicit user interaction.

Currently implemented features:


Automatic libdir setup to $exec_prefix/lib or $exec_prefix/lib64


Depending on architecture, site script should correctly and
automatically switch between lib and lib64 libdir.


libexecdir setup to $exec_prefix/lib


Upstream libexecdir defaults to $exec_prefix/libexec. This directory is
not part of FHS 2.2, so we change it to $exec_prefix/lib (yes, it is
correct to set it to $exec_prefix/lib even for bi-arch platforms). Most
projects add package name to this path, so you most probably get what
FHS 2.2 expects.

--
nosy: +catalin.iacob

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Roumen Petrov]

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 flexible instead you hard coded stuff in configure script.

--
nosy: +rpetrov

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Roumen Petrov]

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 rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Skip Montanaro]

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 python-l...@python.org.  Someone directed me to this open bug 
report.  I saw the reference to the patch, applied it, and installed.  I 
verified that the installed Python executable now works as I expected, and 
reported that.  That is all I did.  Various responses seem to suggest that 
people think I wrote the patch.  I did not.  I didn't even look at the contents 
of the patch before applying it.  I regenerated it relative to the current hg 
trunk simply because when I first applied it, a couple chunks were applied with 
offsets.

If my feedback is not sufficient to help move this bug report forward, my 
apologies.  I know next to nothing about writing configure scripts, let alone 
the right way to do that.  I don't mess around at this level of things any 
more.  Haven't in at least a decade.  I don't know what a host macro is.  I 
have never used --libdir.  If people are looking to me to correct the flaws in 
this patch, they are likely going to wait for awhile.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Matthias Klose]

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 to overwrite for cross builds. If these macros
   are needed then they should be taken from the sysconfig module,
   using the _sysconfigdata module.

 - use the host macros in the configure instead of uname

 - LIB shouldn't be necessary when configuring --with-libdir

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Skip Montanaro]

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 difficult to overwrite for cross builds. If these macros
are needed then they should be taken from the sysconfig module,
using the _sysconfigdata module.

  - use the host macros in the configure instead of uname

  - LIB shouldn't be necessary when configuring --with-libdir

Sorry, I don't have access to anything but the OpenSUSE systems at
work.  I was just verifying that it solved my installation problems.
I'll see if I can nudge some of the other things forward.

--
title: Python 3.3/3.4 installation issue  on OpenSUSE lib/lib64 folders - 
Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Skip Montanaro]

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 perfectly (two chunks were slightly offset), so I 
generated a new patch, which is attached.

It's been awhile since I did anything with bug reports.  I tweaked a few 
fields.  Let me know if I muffed anything.

--
keywords: +patch
nosy: +skip.montanaro
stage:  - patch review
title: Python 3.3 beta 1 installation issue lib/lib64 folders - Python 3.3/3.4 
installation issue  on OpenSUSE lib/lib64 folders
versions: +Python 3.4
Added file: http://bugs.python.org/file27445/opensuse.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com