This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: symbol _dl_global_scope problem
- From: "H. J. Lu" <hjl at lucon dot org>
- To: Kein Yuan <kein dot yuan at gmail dot com>
- Cc: GNU C Library <libc-alpha at sources dot redhat dot com>
- Date: Mon, 18 Apr 2005 06:57:19 -0700
- Subject: Re: symbol _dl_global_scope problem
- References: <d0cf8c905041723591f39a33@mail.gmail.com>
On Mon, Apr 18, 2005 at 02:59:11PM +0800, Kein Yuan wrote:
> I am runing on the same platform with two different configuration:
>
> A, linux 2.6.9 + arm-linux-gcc 3.4.3 + glibc 2.3.2
> B, linux 2.4.17 + arm-linux-gcc -2.95.3 with glibc 2.1.3
>
> also I have a application binary(only binary, and that's the problem)
> which can run on configuration B, but failed on configuration A, it
> shows:
>
> [root@Linux onewave]#./player
> ./player : relocation error: /lib/libdl.so.2: symbol _dl_global_scope, versio
> n GLIBC_2.0 not defined in file ld-linux.so.2 with link time reference
Please provide the output of
# readelf --wide -dsr /lib/ld-linux.so.2 /lib/libdl.so.2 ./player | grep _dl_global_scope
on both systems.
>
> I think it may caused by different glibc, since the application was
> built with gcc2.95.3 and glibc 2.1.3 but on configuration A we just
> have glibc 2.3.2
>
> Does anybody know how I can let the application run ok on configuration A?
>
>
H.J.