Bug#222183: Circular reference in ldconfig cache
At Sat, 03 Jul 2004 02:09:31 +0900,
GOTO Masanori wrote:
> At Wed, 26 Nov 2003 00:42:05 +0000,
> Linas Jakucionis wrote:
> > When trying to start progam Qixite I get the following error message:
> >
> > qixite: relocation error: qixite: undefined symbol: initPAnsiStrings
> >
> > This message usually means that Kylix 3 libraries are not installed, but
> > I have these installed and had them working until I have recently done
> > apt-get upgrade.
> >
> > This is what I have in /etc/ld.so.conf:
> > /usr/X11R6/lib
> > /usr/lib/kylix3
> >
> > This is the output of "ls -l /usr/lib/kylix3/":
> > total 7364
> > lrwxrwxrwx 1 root root 23 Nov 25 00:19 libborqt-6.9-qt2.3.so -> libborqt-6.9.0-qt2.3.so
> > -rw-r--r-- 1 root root 7526184 Nov 3 2002 libborqt-6.9.0-qt2.3.so
> >
> > This is the output of "ldconfig -v | grep -B 1 bor"
> > /usr/lib/kylix3:
> > libborqt-6.9.0-qt2.3.so -> libborqt-6.9.0-qt2.3.so
> >
> > Note that in the /usr/lib/kylix3 I have a symbolic link and the
> > ldconfig show the circular reference... :/
>
> Your point is no problem. For example:
>
> gotom@moog:~> mkdir -p ~/lib
> gotom@moog:~> cd lib
> gotom@moog:~/lib> sudo mv /usr/lib/libbz2.so.1.0.2 .
> gotom@moog:~/lib> objdump -p libbz2.so.1.0.2 | grep SONAME
> SONAME libbz2.so.1.0
> gotom@moog:~/lib> mv libbz2.so.1.0.2 libbz2.so.1.0
> gotom@moog:~/lib> sudo ldconfig -v |& grep libbz
> libbz2.so.1.0 -> libbz2.so.1.0
> gotom@moog:~/lib> grep /home/gotom/lib /etc/ld.so.conf
> /home/gotom/lib
> gotom@moog:~/lib> ldd /usr/bin/bzip2|grep bz2
> libbz2.so.1.0 => /home/gotom/lib/libbz2.so.1.0 (0x40031000)
>
>
> Check SONAME of libborqt-6.9.0-qt2.3.so.
>
> > If I move both files from the /usr/lib/kylix3 to /usr/lib the program
> > starts fine.
>
> I don't know why your movement makes the program start fine.
>
> I think this bug is not glibc, but your application side issue.
> If you have no objection, I'll close this bug.
I discussed with Daniel Jacobowitz on IRC. He pointed out that it
might be ldconfig problem (Thanks Daniel!). We sometimes got problems
about ldconfig.
Please check SONAME with objdump -p. It's needed to investigate, so
we need more information from you. You pointed that moving the
program worked fine. It may be key.
Regards,
-- gotom
Reply to: