You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
~/l/t/perf perf 118ms 2023년 08월 30일 (수) 오전 11시 49분 11초perf: error while loading shared libraries: libpython3.12.so.1.0: cannot open shared object file: No such file or directory
however asdf reshim python will not add shared objects to ~/.asdf/shims/python. i could just add ~/.asdf/installs/python/3.12.0b3/lib/ to LD_LIBRARY_PATH, but this would be fragile when version changes.
would there be a better way to manage this problem?
The text was updated successfully, but these errors were encountered:
scarf005
changed the title
preferred way to share libpython3.so?
preferred way to export libpython3.so to ldd?
Aug 30, 2023
Provide environment information
OS: Linux TG02 6.5.0-stock #1 SMP PREEMPT_DYNAMIC Wed Aug 30 11:09:37 KST 2023 x86_64 x86_64 x86_64 GNU/Linux SHELL: fish, version 3.6.1 ASDF VERSION: v0.11.1-27c8a10 ASDF ENVIRONMENT VARIABLES: ASDF_DIRENV_BIN=/home/scarf/.asdf/installs/direnv/2.32.3/bin/direnv ASDF INSTALLED PLUGINS: direnv https://github.com/asdf-community/asdf-direnv.git master 1a140d6 golang https://github.com/kennyp/asdf-golang.git master f006a12 gradle https://github.com/rfrancis/asdf-gradle.git master e47df00 java https://github.com/halcyon/asdf-java.git master 89f431e kotlin https://github.com/asdf-community/asdf-kotlin.git master af9ab2c nodejs https://github.com/asdf-vm/asdf-nodejs.git master c9e5df4 pnpm https://github.com/jonathanmorley/asdf-pnpm.git master ea033db python https://github.com/danhper/asdf-python.git master 8505457
To Reproduce
Describe the Bug
perf
tool could not findlibpython3.12.so.1.0
.Expected Behaviour
asdf installs has
however
asdf reshim python
will not add shared objects to~/.asdf/shims/python
. i could just add~/.asdf/installs/python/3.12.0b3/lib/
toLD_LIBRARY_PATH
, but this would be fragile when version changes.would there be a better way to manage this problem?
The text was updated successfully, but these errors were encountered: