-
oninoshiko
I know r38 is no longer LTS, but I just started seeing python3.9 showing "ld.so.1: python3.9: fatal: libc.so.1: version 'ILLUMOS_0.39' not found (required by file /usr/lib/amd64/libpython3.9.so.1.0)". any idea how that could be fixed?
-
|cos|
oninoshiko: with least pain, by upgrading? there seem to be no 'ILLUMOS_0.xx' in libc.so.1 on my r38 either, but python-39 still works. later releases has heaps of 'ILLUMOS_0.xx' in libc. dunno more than that, sorry.
-
andyf
oninoshiko - the easiest way is to go back to the old boot environment and `pkg update -f`
-
ardeshir
Hello hadfl, I logged this issue with zadm, let me know if there is more information I can add :
omniosorg/zadm #140
-
oninoshiko
unfortunately, this is doing this on fresh installs for me.
-
oninoshiko
it might be something off with my private repo... but I don't see how that could happen. it doesn't provide libc or python.
-
andyf
There was a change in r38 a while ago, where python started to require the memrchr() function from libc, and I think that is what you are hitting.
-
andyf
It sounds like you have a newer python and an older libc, which should not be possible - there are some dependencies in place that should stop it happening, although the way it was done was not the best, it should work.
-
oninoshiko
hrm... I'm running a local mirror of the r38 repo. maybe the last time I updated it something didn't make it
-
andyf
It would be interesting to list the versions of `system/library` and `python-39` that are in there
-
oninoshiko
I'll check it in a bit, right now it's running a verify
-
andyf
With local access `pkgrepo -s /path/ list python-39 library` should work
-
andyf
You want omnios system/library 0.5.11-151038.0:20220407T165903Z
-
oninoshiko
omnios runtime/python-39 3.9.17-151038.0:20230614T205750Z
-
oninoshiko
omnios system/library 0.5.11-151038.0:20210427T213425Z
-
oninoshiko
those look consistant with what's on the main repo
-
richlowe
there should be a bunch of ILLUMOS_* revs, whether python needs them depends on which symbols in libc it actually uses
-
richlowe
you can use pvs(1) to look at stuff like this
-
richlowe
so `pvs -sd libc.so.1` will show you which versions exist, and which symbols are within them, `pvs -s python` will tell you what it wants, though deeply unbelievably
-
richlowe
(perhaps you linked python with gld?)
-
richlowe
or perhaps because it's all in libpython really.
-
richlowe
yes, pvs -s libpython3.11.so is more useful
-
richlowe
hopefully that brain dump gets you someplace?
-
hadfl
oninoshiko, your system/library definitely seems outdated. this is what i get when i query the r38 repo
-
hadfl
hadfl@nemesis:~$ pkg list -H -avf -g
pkg.omnios.org/r151038/core system/library | head -1
-
hadfl
pkg://omnios/system/library⊙0:20220407T165903Z ---
-
oninoshiko
whoops, 5.11-151038.0:20220407T165903Z
-
oninoshiko
I did a diff `
-
oninoshiko
I did a diff `/usr/bin/pkgrepo -s
pkg.omnios.org/r151038/core list | diff -u - <(pfexec /usr/bin/pkgrepo -s /Array-0/pkg/r151038/core/ list)` to check it