On Mon, 25 Nov 2002, Kurt Wall wrote: > On Mon, Nov 25, 2002 at 11:42:35AM -0500, Net Llama! wrote: > > > > > > Does this mean that the problem is with /lib/libpthread.so.0 ? > > Possibly.
Nope, turned out to be the symlink: /lib/libc.so.6 -> /lib/libc-2.2.5.so I still can't figure out how that got set before i did a make install. > > > I think i've figured out (part of) thje problem. Somehow, and i've yet to > > figure out how, when i was attempting to build glibc-2.2.5 last week, > > parts of it got installed. I have no idea how, since the build bombed out > > (ironically with a core dump) and i never even got as far as the 'make > > install' phase. > > I know that GLIBC has a fix-includes script that modifies header > files so they'll work properly after the new library is installed, > so perhaps that's the cause? Well, no, that isn't it; modifying header > files shouldn't affect applications that are already compiled. I > think you've got library version mismatches, which will most definitely > cause seg faults. I'd reinstall the original library binaries if that's > possible. Thankfully i backed up /lib before doing the initial build of glibc-2.2.5, so i just restored that and there are no more core dumps. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman [EMAIL PROTECTED] Linux Step-by-step & TyGeMo http://netllama.ipfox.com _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
