Issue tracker moved to https://gitlab.archlinux.org/archlinux/aurweb/-/issues
FS#5535 - cadaver needs libexpat.so.0
Attached to Project:
AUR web interface
Opened by Henrik Farre (enrique) - Friday, 06 October 2006, 12:57 GMT
Opened by Henrik Farre (enrique) - Friday, 06 October 2006, 12:57 GMT
|
Detailsrunning cadaver fails with:
cadaver: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory ldd `which cadaver` gives: linux-gate.so.1 => (0xffffe000) libreadline.so.5 => /lib/libreadline.so.5 (0xb7eed000) libncurses.so.5 => /lib/libncurses.so.5 (0xb7eaa000) libneon.so.25 => /usr/lib/libneon.so.25 (0xb7e8e000) libz.so.1 => /usr/lib/libz.so.1 (0xb7e7c000) libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb7e3c000) libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb7cfc000) libdl.so.2 => /lib/libdl.so.2 (0xb7cf8000) libgssapi.so.4 => /usr/lib/libgssapi.so.4 (0xb7ce2000) libkrb5.so.17 => /usr/lib/libkrb5.so.17 (0xb7c9b000) libasn1.so.6 => /usr/lib/libasn1.so.6 (0xb7c69000) libcom_err.so.2 => /lib/libcom_err.so.2 (0xb7c65000) libroken.so.16 => /usr/lib/libroken.so.16 (0xb7c54000) libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7c26000) libresolv.so.2 => /lib/libresolv.so.2 (0xb7c14000) libexpat.so.0 => not found libpthread.so.0 => /lib/libpthread.so.0 (0xb7c01000) libc.so.6 => /lib/libc.so.6 (0xb7adf000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7ac0000) /lib/ld-linux.so.2 (0xb7f2f000) libdb-4.4.so => /usr/lib/libdb-4.4.so (0xb79d9000) libexpat.so.0 does not exist on my system, but /usr/lib/libexpat.so does. A simple symlink from libexpat.so.0 to libexpat.so.1.5.0 fixes the problem |
This task depends upon
Closed by Simo Leone (neotuli)
Sunday, 12 November 2006, 21:26 GMT
Reason for closing: Won't fix
Additional comments about closing: This tracker is for AUR interface related bugs, not for AUR package related bugs. For that, please contact the maintainer directly.
Sunday, 12 November 2006, 21:26 GMT
Reason for closing: Won't fix
Additional comments about closing: This tracker is for AUR interface related bugs, not for AUR package related bugs. For that, please contact the maintainer directly.