Bug: running system legacy OS glibc <2.12
See original GitHub issueHi,
On legacy systems we can’t update or install anything, we can’t run the software:
# ldd log4j2-scan
./log4j2-scan: /lib64/libpthread.so.0: version `GLIBC_2.12' not found (required by ./log4j2-scan)
./log4j2-scan: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./log4j2-scan)
It is possible to compile with glibc 2.11?
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
substitute linuxbrew glibc for os glibc · Issue #1011 - GitHub
When compiling a c file I have $ ldd glibc linux-vdso.so.1 ... but the system that I'm running on is glibc 2.12 and...
Read more >How to fix damaged system by removing glibc-2.12-1.212.el6 ...
Hello, this is CentOS release 6.7 and there was an error after removing glibc (wanted to use newer version not offered by yum):....
Read more >How To Patch and Protect Linux Server Against the Glibc ...
Method #2: Run the instructions given in the previous section called GHOST vulnerability check (generic method for all Linux based systems).
Read more >GLIBC version problem - Red Hat Customer Portal
I want to install a Control M Fix Pack 500, but when I put the comand /tmp/ControlM/PAKAI.8.0.00.500_Linux-x86_64_INSTALL.BIN to install the ...
Read more >RedHat update problem after install CPanel
RedHat update problem after install CPanel ... Dependency Resolution Error: Package: glibc-devel-2.12-1.149.el6.i686 (rhel-x86_64-server-6) Requires: glibc ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
but…consider java and log4j hidden within docker containers, snaps, or other items… or java installed outside of your shell $PATH. Personal home directories may cause unwanted exposures.
Exactly, if it were possible to compile with static libraries it would solve!