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)


--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

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.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

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.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On 13 Dec 2024, at 15:54, aotto1968 via Python-list <python-list@python.or=

wrote:

=20
HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading shar=

ed 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 t= hey 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 =3D> /lib64/libpython3.13.so.1.0 (0x0000ffffb7e= a0000)
libc.so.6 =3D> /lib64/libc.so.6 (0x0000ffffb7cd0000)
libm.so.6 =3D> /lib64/libm.so.6 (0x0000ffffb7c20000)
/lib/ld-linux-aarch64.so.1 (0x0000ffffb84d0000)

Barry



--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

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.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

--q73yrbdvrspxcspr
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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".
=20

I think after ~30 years *python* should be able to handle a shared-lib=

rary proper __or__ switch to a *static-build* by default.

=20

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

=20
make[1]: Verzeichnis =E2=80=9EHOME/src/mono.git/acceptance-tests=E2=80=9C=

wird betreten

HOME/ext/x86_64-suse-linux-gnu/debug/bin/python3: error while loading sha=

red

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 =E2=80=9EHOME/src/mono.git/acceptance-tests=E2=80=9C=

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 =3D> HOME/ext/x86_64-suse-linux-gnu/debug/l=

ib64/libpython3.12d.so.1.0 (0x00007f9c5d374000)

libpthread.so.0 =3D> /lib64/libpthread.so.0 (0x00007f9c5d350000)
libdl.so.2 =3D> /lib64/libdl.so.2 (0x00007f9c5d349000)
libutil.so.1 =3D> /lib64/libutil.so.1 (0x00007f9c5d345000)
libm.so.6 =3D> /lib64/libm.so.6 (0x00007f9c5d1f9000)
libc.so.6 =3D> /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

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

--q73yrbdvrspxcspr
Content-Type: application/pgp-signature; name="signature.asc"

-----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 ZTWxMOzkWvLk02lwNHDcP975LdGfOjrVESdnaFncnHCZhekNtfc=
=nPgR
-----END PGP SIGNATURE-----

--q73yrbdvrspxcspr--

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 12/13/24 1:56 PM, aotto1968 via Python-list wrote:

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.

You're mistaken in this case. Nothing you've posted indicates the
problem is in Python itself. Something isn't quite right with your
linker and the linker search paths. LD_LIBRARY_PATH is one way to force
the linker to use the correct search path.

Python has no direct influence over the linker search paths, other than
to list what shared libraries it is linked against, or to manually add
paths to the linker in /etc/ld.so.conf.d/ during package installation.
The ld.so linker is responsible for finding the files and linking them
in, not Python. In your case it seems unable to do so, for whatever
reason. Since your custom version of python3 does seem to link to the so properly, it seems as though something isn't right in the environment of
the mono build process. Again, nothing to do with Python. The linker
isn't even getting to the bit where it links in libpython3.



--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 12/14/24 2:56 AM, Peter J. Holzer via Python-list wrote:

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.

Indeed something is not right with his ld.so search paths. The original
error report indicates the linker cannot even find the libpython so
file, so this cannot be a problem with Python since the linker hasn't
even found it. I don't see how he expects python to fix this
configuration issue magically for mono's build scripts.



--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

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.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On Sun, 15 Dec 2024 at 06:05, aotto1968 via Python-list <python-list@python.org> wrote:

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.

So, it's an environment problem, NOT a Python problem. You messed up
your installation. Start over, rebuild.

ChrisA

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 12/14/24 10:31 AM, aotto1968 via Python-list wrote:

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.

mono build is failing even before you get to running your python3.
That's not something python developers can fix.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

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.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

--77uwacozsxv7kufg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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".

[...]

=20
If I read the answers I come to the conclusion that the "supporters" at p=

ython

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

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

--77uwacozsxv7kufg
Content-Type: application/pgp-signature; name="signature.asc"

-----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/o288QYhZAwpwddEQbofnSevyMCIq0fQXM2+g0=
=w9wK
-----END PGP SIGNATURE-----

--77uwacozsxv7kufg--

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 2024-12-16, aotto1968 via Python-list <python-list@python.org> wrote:

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

You should definitely demand to speak to the manager and request your
money back.

--
Grant


--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 12/16/24 12:08 AM, aotto1968 via Python-list wrote:

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

Sorry you feel that way. Various people gave the best advice they could
based on what you had provided. You were given some good advice and
even a few very specific things to try to determine the root problem
which you don't seem to have done. I've used linux for 30 years and
I've never seen a relative path used for a linker search path. What
provided this path to the linker?

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

I get angry…

next python error…

1) The OpenSUSE command "cnf" checks if a special package feature is installed. 2) I recently compiled **my** SQLite3 library specifically tailored to **my** requirement and installed it in **my** SQLite3
project directory and never changed the OpenSUSE installation.
3) "cnf" seems to use "Python" internally, but is **not** able to configure the *Python* environment to use only "OpenSUSE"'s
own "Python" and "Sqlite3" software.
4) Now the "cnf" fails with "Python" which apparently tries to use **my** SQLite3.

what a shame.

cnf jmc

Traceback (most recent call last):
File "/usr/bin/cnf", line 9, in <module>
import scout
File "/usr/lib/python3.6/site-packages/scout/__init__.py", line 10, in <module>
import sqlite3
File "/usr/lib64/python3.6/sqlite3/__init__.py", line 23, in <module>
from sqlite3.dbapi2 import *
File "/usr/lib64/python3.6/sqlite3/dbapi2.py", line 27, in <module>
from _sqlite3 import *
ImportError: /usr/lib64/python3.6/lib-dynload/_sqlite3.cpython-36m-x86_64-linux-gnu.so: undefined symbol: sqlite3_trace


--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On 25.12.24 12:05, aotto1968 wrote:

I get angry…

next python error…

1) The OpenSUSE command "cnf" checks if a special package feature is installed.
2) I recently compiled **my** SQLite3 library specifically tailored to **my** requirement and installed it in **my** SQLite3
project directory and never changed the OpenSUSE installation.
3) "cnf" seems to use "Python" internally, but is **not** able to configure the *Python* environment to use only "OpenSUSE"'s
own "Python" and "Sqlite3" software.
4) Now the "cnf" fails with "Python" which apparently tries to use **my** SQLite3.

what a shame.

cnf jmc

Traceback (most recent call last):
ÿ File "/usr/bin/cnf", line 9, in <module>
ÿÿÿ import scout
ÿ File "/usr/lib/python3.6/site-packages/scout/__init__.py", line 10, in <module>
ÿÿÿ import sqlite3
ÿ File "/usr/lib64/python3.6/sqlite3/__init__.py", line 23, in <module>
ÿÿÿ from sqlite3.dbapi2 import *
ÿ File "/usr/lib64/python3.6/sqlite3/dbapi2.py", line 27, in <module>
ÿÿÿ from _sqlite3 import *
ImportError: /usr/lib64/python3.6/lib-dynload/_sqlite3.cpython-36m-x86_64-linux-gnu.so: undefined symbol: sqlite3_trace

It is not only an *usage* error it is also an *security* error because:

1) "cnf" is using OS python

head /usr/bin/cnf

#!/usr/bin/python3

import gettext
import os
....

2) os "root" python

ls -al /usr/bin/python3

lrwxrwxrwx 1 root root 9 2. Dez 13:16 /usr/bin/python3 -> python3.6

ls -al /usr/bin/python3.6

-rwxr-xr-x 2 root root 10560 2. Dez 13:16 /usr/bin/python3.6

3) using **my** local non-root library

ls -al NHI1_EXT/lib64/libsqlite3.so.0

lrwxrwxrwx 1 dev1usr users 19 23. Dez 22:09 NHI1_EXT/lib64/libsqlite3.so.0 -> libsqlite3.so.0.8.6

ls -al NHI1_EXT/lib64/libsqlite3.so.0.8.6

-rwxr-xr-x 1 dev1usr users 3851872 23. Dez 22:09 NHI1_EXT/lib64/libsqlite3.so.0.8.6

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list <python-list@python.org> wrote:

It is not only an *usage* error it is also an *security* error because:

1) "cnf" is using OS python
2) os "root" python
3) using **my** local non-root library

Yes. And YOU were the one who installed a new root Python. This is a
feature. You have the power to update Python on your system.

You managed to make a build of Python that attempts to link to a DLL
using a relative path. That's a fault of the build that means it won't
work as root. I don't understand the confusion here; isn't the
solution here to build a new version with an absolute path, and update
your installation?

ChrisA

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 12/25/24 3:55 PM, Chris Angelico via Python-list wrote:

On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list <python-list@python.org> wrote:

It is not only an *usage* error it is also an *security* error because:

1) "cnf" is using OS python
2) os "root" python
3) using **my** local non-root library

I think he means the cnf is using the "root" OS python in /usr/bin, but /usr/bin/python3 is trying to import his local build of sqlite3, which
cause it to fail. I assume he would like cnf to not try to import his
local sqlite3, and instead use the normal system one. If this is the
case, then somehow his local, non-root sqlite3 library is being picked
up by the system version of python.

Aotto might want to run the "env" command and see if there are any
search paths that have to do with Python. I can see how this could be a security issue. If you can figure out what's happening you might want to
open a ticket with the OpenSUSE developers. This is Python related, but
it's not necessarily python's fault per se.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 12/25/24 8:55 PM, Michael Torrie wrote:

This is Python related, but
it's not necessarily python's fault per se.

It's also a good reminder to use venv. Then there's no way of
activating your custom python with its custom sqlite3 library unless you explicitly activate the venv.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On Thu, 26 Dec 2024 at 14:57, Michael Torrie via Python-list <python-list@python.org> wrote:

On 12/25/24 3:55 PM, Chris Angelico via Python-list wrote:

On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list <python-list@python.org> wrote:

It is not only an *usage* error it is also an *security* error because:

1) "cnf" is using OS python
2) os "root" python
3) using **my** local non-root library

I think he means the cnf is using the "root" OS python in /usr/bin, but /usr/bin/python3 is trying to import his local build of sqlite3, which
cause it to fail. I assume he would like cnf to not try to import his
local sqlite3, and instead use the normal system one. If this is the
case, then somehow his local, non-root sqlite3 library is being picked
up by the system version of python.

Right. That's exactly what would happen if he'd built Python using
absolute paths to libraries, which is the normal way to do it. And so
the solution is to rebuild Python using absolute paths to libraries.

ChrisA

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 25.12.24 23:55, Chris Angelico wrote:

On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list <python-list@python.org> wrote:

It is not only an *usage* error it is also an *security* error because:

1) "cnf" is using OS python
2) os "root" python
3) using **my** local non-root library

Yes. And YOU were the one who installed a new root Python. This is a
feature. You have the power to update Python on your system.

You managed to make a build of Python that attempts to link to a DLL
using a relative path. That's a fault of the build that means it won't
work as root. I don't understand the confusion here; isn't the
solution here to build a new version with an absolute path, and update
your installation?

ChrisA

sorry you don't understand the problem…

You managed to make a build of Python that attempts to link to a DLL

I never touch the OpenSUSE python. the OpenSUSE python try to use my
sqalite3.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On 26.12.24 06:46, Chris Angelico wrote:

On Thu, 26 Dec 2024 at 14:57, Michael Torrie via Python-list <python-list@python.org> wrote:

On 12/25/24 3:55 PM, Chris Angelico via Python-list wrote:

On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list
<python-list@python.org> wrote:

It is not only an *usage* error it is also an *security* error because: >>>>
1) "cnf" is using OS python
2) os "root" python
3) using **my** local non-root library

I think he means the cnf is using the "root" OS python in /usr/bin, but
/usr/bin/python3 is trying to import his local build of sqlite3, which
cause it to fail. I assume he would like cnf to not try to import his
local sqlite3, and instead use the normal system one. If this is the
case, then somehow his local, non-root sqlite3 library is being picked
up by the system version of python.

Right. That's exactly what would happen if he'd built Python using
absolute paths to libraries, which is the normal way to do it. And so
the solution is to rebuild Python using absolute paths to libraries.

ChrisA

next I don't change the OpenSUSE python and the OpenSUSE python is using *my* sqlite3.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On 26.12.24 04:55, Michael Torrie wrote:

On 12/25/24 3:55 PM, Chris Angelico via Python-list wrote:

On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list
<python-list@python.org> wrote:

It is not only an *usage* error it is also an *security* error because:

1) "cnf" is using OS python
2) os "root" python
3) using **my** local non-root library

I think he means the cnf is using the "root" OS python in /usr/bin, but /usr/bin/python3 is trying to import his local build of sqlite3, which
cause it to fail. I assume he would like cnf to not try to import his
local sqlite3, and instead use the normal system one. If this is the
case, then somehow his local, non-root sqlite3 library is being picked
up by the system version of python.

Aotto might want to run the "env" command and see if there are any
search paths that have to do with Python. I can see how this could be a security issue. If you can figure out what's happening you might want to
open a ticket with the OpenSUSE developers. This is Python related, but
it's not necessarily python's fault per se.

Yes I using with *my* user *my* environment but never touch the *root* environment at all.

the *root* python try to use *my* sqlite3 because *my* environment
fit to *my* needs.

/* just a reminder */

sqlite3 have a "special" (worse) setup that a change to the configuration
also change the "api" ( a sqlite_function disappear or arrive ).
If a tool like python using an extension that is linked to sqlite3 that extension
will likely FAIL is I get an OTHER sqlite3 which is NOT the one the extension was build with.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On 26.12.24 04:55, Michael Torrie wrote:

On 12/25/24 3:55 PM, Chris Angelico via Python-list wrote:

On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list
<python-list@python.org> wrote:

It is not only an *usage* error it is also an *security* error because:

1) "cnf" is using OS python
2) os "root" python
3) using **my** local non-root library

I think he means the cnf is using the "root" OS python in /usr/bin, but /usr/bin/python3 is trying to import his local build of sqlite3, which
cause it to fail. I assume he would like cnf to not try to import his
local sqlite3, and instead use the normal system one. If this is the
case, then somehow his local, non-root sqlite3 library is being picked
up by the system version of python.

Aotto might want to run the "env" command and see if there are any
search paths that have to do with Python. I can see how this could be a security issue. If you can figure out what's happening you might want to
open a ticket with the OpenSUSE developers. This is Python related, but
it's not necessarily python's fault per se.

You don't understand the problem if you think "/usr/bin/env" will solve the problem → this will make it more worse.

A "personal" python will use a "personal" configuration and probably is *not* build with sqlite3 support at all.

a *root* tool should never ever use/call a non *root* (personal) setup.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On 12/25/24 10:46 PM, Chris Angelico wrote:

Right. That's exactly what would happen if he'd built Python using
absolute paths to libraries, which is the normal way to do it. And so
the solution is to rebuild Python using absolute paths to libraries.

You're right. Definitely appears to be a pretty major mis-configuration
of his system. Not much we can do about that.


--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 26.12.24 19:33, Michael Torrie wrote:

On 12/25/24 10:46 PM, Chris Angelico wrote:

Right. That's exactly what would happen if he'd built Python using
absolute paths to libraries, which is the normal way to do it. And so
the solution is to rebuild Python using absolute paths to libraries.

You're right. Definitely appears to be a pretty major mis-configuration
of his system. Not much we can do about that.

no, your are wrong.

The problem is NOT that my user-account has a miss-configuration because my user-account works pretty well…

The problem is that the *default* /usr/bin/python3 OpenSUSE installation using parts of *my* local *user* setup.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)