[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Change by Xavier de Gaye : -- nosy: -xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Xavier de Gaye added the comment: The problem is that Makefile and Modules/getpath.c are not consistent: * Makefile uses $(LIBDIR)/python$(VERSION)/lib-dynload as the location of the installed shared libraries and in this issue, it happens that LIBDIR is not ${exec_prefix}/lib but is

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Xavier de Gaye added the comment: The problem can be reproduced as follows: Run the following commands to install python with a site configuration file that installs the libraries to lib64: export INSTALL_DIR=/some/path/to/install mkdir -p $INSTALL_DIR/share echo "test \"\$libdir\" =

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Xavier de Gaye added the comment: > Sorry that I haven't answered for a long time. I would like to get an email > notification but I don't know whether/how I can enable it. You should get an email upon each message posted to this issue. The email is sent to the address you have registered

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Johannes S. added the comment: Sorry that I haven't answered for a long time. I would like to get an email notification but I don't know whether/how I can enable it. On "my instance of Linux SuSE", the lines are locking like this: CONFIG_ARGS=' '\''--prefix=/some/dir'\'''

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Xavier de Gaye added the comment: Johannes, what are the values of CONFIG_ARGS and libdir in the config.log of your Linux SuSE. -- nosy: +xdegaye ___ Python tracker

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Johannes S. added the comment: Maybe my last comment was not clear enogth. I used the tarballs from 3.5 and 3.6 which are linked in my last comment. I extracted them and run the the following commands on Arch (64 Bit) and Linux SuSE 13.1 (64 Bit): mkdir build cd build ../configure

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Ned Deily added the comment: Sorry, it is no longer clear to me exactly what problem(s) and solution are being proposed here. When dealing with installation problems like this, we have to be *very* precise: here's what I started with on what platform, here are the contents of the relevant

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Johannes S. added the comment: I tried it again and I also tried 3.6.0a1 now. 3.6.0a1 has the issue as well. I have downloaded the tarballs from https://www.python.org/downloads/release/python-351/ and https://www.python.org/downloads/release/python-360a1/. I have run it on my Laptop (Arch

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Ned Deily added the comment: That's very odd! I don't have a SuSE system available to test with but it is not clear to me why that would have different behavior because where the standard library extension modules directory (lib-dynload) is installed is controlled by the Python configure and

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Johannes Spangenberg added the comment: I can confirm this issue. I did run it on Linux SuSE 13.1 (64 Bit). Unlike other components, which are installed in `lib/`, `lib-dynload` is installed in `lib64/python3.5/`. But `sys.path` still points to `lib/python3.5/lib-dynload`. It did run in on :

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Ned Deily added the comment: Sorry, I'm not able to reproduce your results on a vanilla Debian system. Building from scratch with ./configure --prefix=/usr and make steps results in: $ /usr/bin/python3.5 Python 3.5.1 (default, May 22 2016, 02:26:09) [GCC 4.9.2] on linux Type "help",

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

Jaroslav Urban added the comment: just a remark, my system is $uname -r 4.4.5-200.fc22.x86_64 and these python-related rpm archives are installed: $rpm -qa | grep python python-IPy-0.81-12.fc22.noarch python-urllib3-1.13.1-3.fc22.noarch libselinux-python-2.3-10.fc22.x86_64

[issue26971] python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARED

New submission from Jaroslav Urban: #wget https://www.python.org/ftp/python/3.5.1/Python-3.5.1.tar.xz #xz -d Python-3.5.1.tar.xz #tar xvf Python-3.5.1.tar #cd Python-3.5.1 #./configure --prefix=/usr #make #make altinstall --- so far so good but afterwards