On 13.12.24 11:36, aotto1968 wrote:

it's a shame...
almost every tool I touch that uses "python" in some way has some configuration error because apparently a __private__ python
installation __isn't__ properly "understood".

I think after ~30 years *python* should be able to handle a shared-library proper __or__ switch to a *static-build* by default.

example here is the "mono-build" with the following installation.

1. The build is done with my user and the installation is done as root.
2. The setup proper find *my* python3 because my PATH etc is setup well.
3. root is an other environment and root does *not* have my environment.
4. root uses *my* python3 without *my* environment and is *not* able to find
*my* libpython3.12d.so.1.0
5. obviously the *python3* is *not* able to create the right environment from
the installation directory of the *python3* executable.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 13.12.24 11:44, aotto1968 wrote:

On 13.12.24 11:36, aotto1968 wrote:

it's a shame...
almost every tool I touch that uses "python" in some way has some configuration error because apparently a __private__ python
installation __isn't__ properly "understood".

I think after ~30 years *python* should be able to handle a shared-library proper __or__ switch to a *static-build* by

default.

example here is the "mono-build" with the following installation.

1. The build is done with my user and the installation is done as root.
2. The setup proper find *my* python3 because my PATH etc is setup well.
3. root is an other environment and root does *not* have my environment.
4. root uses *my* python3 without *my* environment and is *not* able to find
   *my* libpython3.12d.so.1.0
5. obviously the *python3* is *not* able to create the right environment from
  the installation directory of the *python3* executable.

even the `sudo -E make install` with "-E, --preserve-env" does help.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

it's a shame...
almost every tool I touch that uses "python" in some way has some configuration error because apparently a __private__ python
installation __isn't__ properly "understood".

I think after ~30 years *python* should be able to handle a shared-library proper __or__ switch to a *static-build* by default.

example here is the "mono-build" with the following installation.

make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird betreten HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory
make[2]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird betreten HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory
make[2]: Für das Ziel „install-exec-am“ ist nichts zu tun.
make[2]: Für das Ziel „install-data-am“ ist nichts zu tun.
make[2]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird verlassen make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird verlassen [debug]dev1usr@linux02:~/src/mono.git> ldd HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3
linux-vdso.so.1 (0x00007ffd18e9a000)
libpython3.12d.so.1.0 => HOME/ext/x86_64-suse-linux-gnu/debug/lib64/libpython3.12d.so.1.0 (0x00007f9c5d374000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9c5d350000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f9c5d349000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007f9c5d345000)
libm.so.6 => /lib64/libm.so.6 (0x00007f9c5d1f9000)
libc.so.6 => /lib64/libc.so.6 (0x00007f9c5d002000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9c5dab4000)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 13 Dec 2024, at 15:54, aotto1968 via Python-list <python-list@python.org> wrote:

HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open shared object file: No such file or directory

This is a debug build?

Try setting LD_LIBRARY_PATH to point at the folder that contains the .so.
Test with `ldd python3` which will show which .so libs python3 needs and if they are found.

This is what I see on Fedora 41 as an example of the output.

$ ldd /usr/bin/python3
linux-vdso.so.1 (0x0000ffffb8515000)
libpython3.13.so.1.0 => /lib64/libpython3.13.so.1.0 (0x0000ffffb7ea0000)
libc.so.6 => /lib64/libc.so.6 (0x0000ffffb7cd0000)
libm.so.6 => /lib64/libm.so.6 (0x0000ffffb7c20000)
/lib/ld-linux-aarch64.so.1 (0x0000ffffb84d0000)

Barry

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 13.12.24 19:24, Barry wrote:

On 13 Dec 2024, at 15:54, aotto1968 via Python-list <python-list@python.org> wrote:

HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open shared object file: No such file or directory

This is a debug build?

Try setting LD_LIBRARY_PATH to point at the folder that contains the .so. Test with `ldd python3` which will show which .so libs python3 needs and if they are found.

This is what I see on Fedora 41 as an example of the output.

$ ldd /usr/bin/python3
linux-vdso.so.1 (0x0000ffffb8515000)
libpython3.13.so.1.0 => /lib64/libpython3.13.so.1.0 (0x0000ffffb7ea0000)
libc.so.6 => /lib64/libc.so.6 (0x0000ffffb7cd0000)
libm.so.6 => /lib64/libm.so.6 (0x0000ffffb7c20000)
/lib/ld-linux-aarch64.so.1 (0x0000ffffb84d0000)

Barry

the problem is *not* to setup an environment variable, the problem is that python is *not*
able to setup the *python* environment by it self.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2024-12-13 11:36:01 +0100, aotto1968 via Python-list wrote:

it's a shame...
almost every tool I touch that uses "python" in some way has some configuration error because apparently a __private__ python installation __isn't__ properly "understood".

I think after ~30 years *python* should be able to handle a shared-library proper __or__ switch to a *static-build* by default.

example here is the "mono-build" with the following installation.

make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird betreten HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open shared object file: No such file or directory

What is HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3 and why is HOME/src/mono.git/acceptance-tests trying to use it?

[...]

make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird verlassen [debug]dev1usr@linux02:~/src/mono.git> ldd HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3
linux-vdso.so.1 (0x00007ffd18e9a000)
libpython3.12d.so.1.0 => HOME/ext/x86_64-suse-linux-gnu/debug/lib64/libpython3.12d.so.1.0 (0x00007f9c5d374000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9c5d350000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f9c5d349000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007f9c5d345000)
libm.so.6 => /lib64/libm.so.6 (0x00007f9c5d1f9000)
libc.so.6 => /lib64/libc.so.6 (0x00007f9c5d002000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9c5dab4000)

So HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3 does find HOME/ext/x86_64-suse-linux-gnu/debug/lib64/libpython3.12d.so.1.0 if you
invoke it from the shell (to confirm that, try actually invoking it
instead of running ldd on it), but not when it's called from whatever
make is doing in the acceptance-tests directory.

So it might be because it's in a different directory ("HOME/ext/..." is
a relative path. That will not work in a different directory. Also
"HOME" is a strange choice for a directory name. Did you mean $HOME?) or because the acceptance tests set up their own environment.

I'd test the first idea first. Cd into
HOME/src/mono.git/acceptance-tests and try to invoke HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3 there.

hp

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmddVmMACgkQ8g5IURL+ KF01EhAAh1P7PRabv8pDWVNowLB5xxy9J7esqHcdMaleIa0TBNN2DnsVaVBLPAkH FOOm8gLQzC82Ia810NmUlM2QcK7OmnpMg62SrDX6+y1+nNLACdwSEFqyP7g/bCJQ w0eogtIhu2ZDDz8/rdMBIPSI+P/JNQuxJuDUFcLDzw6LJe3Fn63FqJQ/euV2YyKx mcnrMbwI7mw4FEcmE9luOmmnBrjjGwFJjA857IKvWnAAMGuyjm3WF1S3wp+bE+gI 0HEhya13T4M67KTZpUuRjDzUh8KGYhwtALv38B7+8dHEmBgQhQlrA4iX0gYni0fb IMNG84w6qMrsfg2nz2usatdDh0KNmaphZTiPR9oxjMQwD9FKSHLpyQVpPfPQislj Ck0UbM3fdInYqAOvnVxgixI3AEwJb98xLacGCV0NvRyAEaYPL3qNIW8ryg9w5rT7 pycznGiMACFVFMIsYxluCcBx8HS7aBYtjvHksXkKUSq20vlC/McJEAZW5cXxvBZ0 mpcqzTrmY5+aPRHmipzXPRsNAF6Bnp+N/90FjQknF8FsR5kQyrM1z+Xd3jUKJLUg 6I2M2UwRLhiMYhqFWPy5pq46AmkT/wbgosWhag5J9ECyZsXENxeK8JCeIyn6BlDL ZTWxMOzkWvLk02lwNHDcP975LdGfOjrVESdnaFn

On 14.12.24 10:56, Peter J. Holzer wrote:

On 2024-12-13 11:36:01 +0100, aotto1968 via Python-list wrote:

it's a shame...
almost every tool I touch that uses "python" in some way has some
configuration error because apparently a __private__ python installation
__isn't__ properly "understood".

I think after ~30 years *python* should be able to handle a shared-library proper __or__ switch to a *static-build* by default.

example here is the "mono-build" with the following installation.

make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird betreten >> HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared >> libraries: libpython3.12d.so.1.0: cannot open shared object file: No such
file or directory

What is HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3 and why is HOME/src/mono.git/acceptance-tests trying to use it?

[...]

make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird verlassen >> [debug]dev1usr@linux02:~/src/mono.git> ldd HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3
linux-vdso.so.1 (0x00007ffd18e9a000)
libpython3.12d.so.1.0 => HOME/ext/x86_64-suse-linux-gnu/debug/lib64/libpython3.12d.so.1.0 (0x00007f9c5d374000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9c5d350000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f9c5d349000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007f9c5d345000)
libm.so.6 => /lib64/libm.so.6 (0x00007f9c5d1f9000)
libc.so.6 => /lib64/libc.so.6 (0x00007f9c5d002000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9c5dab4000)

So HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3 does find HOME/ext/x86_64-suse-linux-gnu/debug/lib64/libpython3.12d.so.1.0 if you invoke it from the shell (to confirm that, try actually invoking it
instead of running ldd on it), but not when it's called from whatever
make is doing in the acceptance-tests directory.

So it might be because it's in a different directory ("HOME/ext/..." is
a relative path. That will not work in a different directory. Also
"HOME" is a strange choice for a directory name. Did you mean $HOME?) or because the acceptance tests set up their own environment.

I'd test the first idea first. Cd into
HOME/src/mono.git/acceptance-tests and try to invoke HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3 there.

hp

The CORE problem is that python3 works well in *my* environment but the installation is done as root and root does not use *my* environment.

the mono build search for a working python3 and find *my*

HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3

The build is fine but after switch to root for installation

sudo make install

the root user call *my* python3 and fail.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 13.12.24 11:36, aotto1968 wrote:

it's a shame...
almost every tool I touch that uses "python" in some way has some configuration error because apparently a __private__ python
installation __isn't__ properly "understood".

I think after ~30 years *python* should be able to handle a shared-library proper __or__ switch to a *static-build* by default.

example here is the "mono-build" with the following installation.

make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird betreten HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shared libraries: libpython3.12d.so.1.0: cannot open
shared object file: No such file or directory
make[2]: Für das Ziel „install-exec-am“ ist nichts zu tun.
make[2]: Für das Ziel „install-data-am“ ist nichts zu tun.
make[2]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird verlassen make[1]: Verzeichnis „HOME/src/mono.git/acceptance-tests“ wird verlassen [debug]dev1usr@linux02:~/src/mono.git> ldd HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3
        linux-vdso.so.1 (0x00007ffd18e9a000)
        libpython3.12d.so.1.0 => HOME/ext/x86_64-suse-linux-gnu/debug/lib64/libpython3.12d.so.1.0 (0x00007f9c5d374000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9c5d350000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f9c5d349000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00007f9c5d345000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f9c5d1f9000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f9c5d002000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f9c5dab4000)

If I read the answers I come to the conclusion that the "supporters" at python doesn't ever understand the problem.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2024-12-16 08:08:46 +0100, aotto1968 via Python-list wrote:

On 13.12.24 11:36, aotto1968 wrote:

it's a shame...
almost every tool I touch that uses "python" in some way has some configuration error because apparently a __private__ python installation __isn't__ properly "understood".

[...]

If I read the answers I come to the conclusion that the "supporters" at python

We are not "the supporters at python". None of us is paid for doing
support. Most of us are just users of Python discussing the language and helping each other when we can (some of us are also contributors to
Python).

doesn't ever understand the problem.

Quite possibly, but in that case you haven't explained it well enough.

hp

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmdgR6cACgkQ8g5IURL+ KF0taQ/+PwGYRa7jzGzQJtKL7kkzzOYzD6pNe8jVxRHdJ/zjywgDw9EYZytLP6Uw jKd7p26JkGWKsoKt2rYAj7FCwICP+HEoGnNeLXUeZXzIFWRT49F1A9OsWKpK9xVn zh6+gywcQR6Ud+e3BAjExUqY2j3pKF3dpnA3Q+AclmruU5CSd+ykHH7LEYaeI6Tx i5iM+wIO4a8bGEleoBYqpARvfBRiR87dI7691TdikrqcnL5f8VeGGtjRjOl1jqBO lk1OWiePc3OzlO26UeZQNGIzkHr48d1uj3Eoa42auGslwNoAoPMP6CSypYgUh/I/ mS5pdLE08fdwL5ryWsj/WHvVuBo2+RFsbVTY/6F/7Vz/ZCOC/fPFrXKD8LO7x3Y9 4A/LIKms0iyS0Vdxt7kHWEZ6Ou7Ols43pVjmU/HKFSCjW6YHrQv1k8M9pkIbsOfy VXmJo29ry7v01QwyP9Q+fw2y0qc5GyvmJPo5NVgCV/r7mWXskyvNUekMsW9hw/uc hJNMDaSa1zHnx8ImdJIQcjb1AHogWd/ml9b7BkNI+qbSmK1iESKg2+QdwMAQyJGt /jU/cEiwY1LNwvDENF8jEOtxzHWAJVbRHA+kg3g6ilexkQy766Y98Ib8Jht3SxBY 6UunnrvNH7Z9V/o288QYhZAwpwddEQbofnSevyM