Public bug reported:
I'm not sure of the right package - it might also depend on the
solution.
Anyway, we have a symlink from /usr/lib64 -> /usr/lib, but there is no
corresponding /usr/local/lib64 -> /usr/local/lib symlink.
This can be a problem when you install libraries outside the package
management system.
We could either add such a symlink, or fix ld.so.conf to have
/usr/local/lib64 in chain of directories it looks at.
Testcase is to install fluidsynth from trunk, which then happily calls
the right binary, which in turn calls the wrong library to do all the
work.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libc-bin 2.12.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Sun Oct 17 15:19:25 2010
Dependencies:
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100826)
ProcEnviron:
LANG=sv_SE.utf8
SHELL=/bin/bash
SourcePackage: eglibc
** Affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug maverick
--
/usr/local/lib64 not in ld.so.conf
https://bugs.launchpad.net/bugs/662153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
