This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: 2.2.94 Problem
Greg Schafer <gschafer@zip.com.au> writes:
> On Sun, Sep 22, 2002 at 03:45:55PM +1000, Greg Schafer wrote:
>> On Sun, Sep 22, 2002 at 07:28:00AM +0200, Andreas Jaeger wrote:
>> > > Core was generated by `/static/bin/bash'.
>> > > Program terminated with signal 11, Segmentation fault.
>> > > #0 0x080ef09a in elf_machine_rel.0 ()
>> > > (gdb) bt
>> > > #0 0x080ef09a in elf_machine_rel.0 ()
>> > > #1 0x080ef34a in elf_dynamic_do_rel.4 ()
>> > > #2 0x080ef4eb in _dl_relocate_object ()
>> > > #3 0x080e93d1 in dl_open_worker ()
>> > > #4 0x080d4ee4 in _dl_catch_error ()
>> > > #5 0x080e94e6 in _dl_open ()
>> > > #6 0x080d593a in do_dlopen ()
>> > > #7 0x080d4ee4 in _dl_catch_error ()
>> > > #8 0x080d58f2 in dlerror_run ()
>> > > #9 0x080d59c9 in __libc_dlopen ()
>> > > #10 0x080ce767 in __nss_lookup_function ()
>> > > #11 0x080ce3c0 in __nss_lookup ()
>> >
>> > bash needs the shared libnss_* libraries and searches for them. It
>> > seems to get them from your older glibc and those two do not work
>> > together.
>>
>> Hmm, you are correct. If I move libnss_files* and libnss_compat* out of
>> the way, it works.
>>
>> But I have linked bash statically, why is it looking at the shared libs
>> on the new system? Any ideas or suggested workarounds?
>
> Actually, I just found the FAQ entry for this...
>
> But I'd still like to find a decent workaround..
Compile with some non-default prefix, e.g. /usr/local/glibc-2.3,
install everything in there and then link bash using this installation,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj