vdso_time error after current updates
I am running current-64 with alienbobs multilib packages.
After the latest glib / kernel updates I get the following error when starting a binary, which was working before (no source available): "error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument" ldd shows: linux-vdso.so.1 (0x00007fff5a1ff000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f49a931c000) libm.so.6 => /lib64/libm.so.6 (0x00007f49a9017000) libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f49a8e02000) libc.so.6 => /lib64/libc.so.6 (0x00007f49a8a3b000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f49a8836000) /lib64/ld-lsb-x86-64.so.3 => /lib64/ld-linux-x86-64.so.2 (0x00007f49a957f000) Do I have to downgrade glibc or does anyone know a better solution? Thank you, Chris |
|
Hello Michael,
yes I have read it. But I didnt't notice anything special concerning my problem?! |
Sorry Chris, I just wanted to make sure you had actually installed Alien Bob's updates. Apart from this I am not very knowledgable about the multilib approach. I tried it a year or so but I had trouble keeping up with which libraries need compat32 versions. Since the performance was about the same for 32-bit and 64-bit I just switched back to the 32-bit system, it was easier.
I hope you get a more useful person responding! Michael |
Hello Michael,
I found the problem. ld-lsb-x86-64.so.3 in /lib64 was still softlinked to ld-2.15.so (done by hand some time ago for lsb-compatibility). Changing this to ld-2.17.so did it... Thank you anyway, Chris |
All times are GMT -5. The time now is 03:59 PM. |