This is the mail archive of the
mailing list for the glibc project.
Re: Binary apps linked against libdl
- To: email@example.com
- Subject: Re: Binary apps linked against libdl
- From: Christopher Seawood <firstname.lastname@example.org>
- Date: Thu, 22 Apr 1999 16:37:13 -0400 (EDT)
- Reply-To: Christopher Seawood <email@example.com>
On 22 Apr 1999, Andreas Jaeger wrote:
> >>>>> Christopher Seawood writes:
> >> > sh: error in loading shared libraries: /usr/glibc2.0/lib/libc.so.6:
> >> > undefined symbol: _dl_global_scope_end
> You're mixing /lib/ld-linux.so.2 which is hardcoded into every binary
> with another libdl.so.2 which isn't hardcoded:
Doh! So I am. :-< I'm still confused as to why running the application
explicitly using the glibc2.0 ld-linux.so.2 does not work. From what
you've said and what I pasted before, it appears as though it's looking
for the 2.0.7 libdl but is complaining that the libdl it gets (apparently,
the glibc 2.1.1 one) is missing _dl_global_scope_end.
If db2inst execs /bin/sh (which it expects to be ksh), will ksh also use
the glibc 2.0.7 ld-linux.so.2 or does the environment get reset on the
(presumed) execve() or system()?