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