[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 --prefix=/some/dir make make install The path `/some/dir` is a placeholder. The path did not exist before running this commands. After running them on Linux SuSE, I discovered that `libpython3.5m.a`, `pkgconfig/` and `python3.5/lib-dynload` was placed in `/some/dir/lib64` instead of `/some/dir/lib`. On Arch, everything is placed in `/some/dir/lib` but I have the same behavior if I add `--libdir=/some/dir/lib64` to `configure`. With other words: `--libdir` seems to have a default value of "EPREFIX/lib64" instead of "EPREFIX/lib" on my instance of Linux SuSE. Maybe `configure` uses some global configurations here? The problem is, that `sys.path` does point to `/some/dir/lib/lib-dynload` in all cases described above. Since `python3.5/lib-dynload` may be placed in `lib64`, this may cause that python does not run properly after installing it. (Unfortunately, I cannot say much about the configuration of "my instance of Linux SuSE" since I am not the person who set it up. It is a server of my university.) -- status: pending -> open ___ Python tracker <http://bugs.python.org/issue26971> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 Linux) now. The issue did *not* occur there. But I discovered that I can trigger a similar issue by specifying the libdir explicitly with `../configure --prefix="/some/dir" --libdir="/some/dir/lib64"`. I thing it would be reasonable to assume that both issues are related. -- versions: +Python 3.6 ___ Python tracker <http://bugs.python.org/issue26971> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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'\'''
libdir='${exec_prefix}/lib64'
--
___
Python tracker
<http://bugs.python.org/issue26971>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
