Message268856
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.) |
|
Date |
User |
Action |
Args |
2016-06-19 16:48:13 | jojo | set | recipients:
+ jojo, ned.deily, yaro-yaro |
2016-06-19 16:48:13 | jojo | set | messageid: <1466354893.33.0.638639322255.issue26971@psf.upfronthosting.co.za> |
2016-06-19 16:48:13 | jojo | link | issue26971 messages |
2016-06-19 16:48:12 | jojo | create | |
|