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
[22407] Error loading Python lib '/tmp/_MEI7VUFgo/libpython3.7m.so.1.0': dlopen: /lib64/libc.so.6: version 'GLIBC_2.14' not found (required by /tmp/_MEI7VUFgo/libpython3.7m.so.1.0)
When I compile and install glibc-2.14 manually and export as an env variable, I get:
export LD_LIBRARY_PATH=/var/opt/glibc-2.14/lib && /tmp/log4j-finder -b
Traceback (most recent call last):
File "log4j-finder.py", line 29, in<module>
File "/root/.pyenv/versions/3.7.5/lib/python3.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 623, in exec_module
File "platform.py", line 116, in<module>
File "/root/.pyenv/versions/3.7.5/lib/python3.7/site-packages/PyInstaller/loader/pyimod03_importers.py", line 623, in exec_module
File "subprocess.py", line 153, in<module>
ImportError: /var//opt/glibc-2.14/lib/libc.so.6: version `GLIBC_2.15' not found (required by /tmp/_MEIWmgHt6/select.cpython-37m-x86_64-linux-gnu.so)
You guessed it, so I build and compiled glibc-2.15 too, and then it gives again the first error.
What I don't understand is that seemingly it's not using these glibc versions:
[root@server]# ./log4j-finder
[89021] Error loading Python lib '/tmp/_MEI9gY1r0/libpython3.7m.so.1.0': dlopen: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/_MEI9gY1r0/libpython3.7m.so.1.0)
[root@server]#
I am not able to solve this without installing pyhthon3.
on RHEL6 I see:
When I compile and install glibc-2.14 manually and export as an env variable, I get:
You guessed it, so I build and compiled glibc-2.15 too, and then it gives again the first error.
What I don't understand is that seemingly it's not using these glibc versions:
Could you compile the binary also for older versions of glibc, like 2.12? Or perhaps there's some option that does something dynamic, I'm no expert.
The text was updated successfully, but these errors were encountered: