Re: libc.so.5.4.46 binaries
Matthew D. Pitts (mpitts@suite224.net)
Sat, 10 Oct 1998 12:31:05 -0400
----------
> From: doctor@fruitbat.org
> To: linux-kernel@vger.rutgers.edu
> Subject: Re: libc.so.5.4.46 binaries
> Date: Friday, October 09, 1998 8:38 PM
>
> Barry Treahy mumbled something about ...
> >
> > I downloaded libc.so.5.4.46 binaries and installed them on my 2.0.33
> > (Slackware distribution) and was a bit upset when my system chocked
with
> > a last gasp of breath stating the the new library was not ELF?!?! I'm
> > no wizard here, but I know that this shouldn't happen.
>
> Well, I didn't have any problem *installing* the library and bringing
> up the system, but once it was up, certain things would no-longer work.
> For example: running "make" would core dump all the time. An strace of
> make shows it getting a SIGSEGV right after a stat() call for an RCS
> directory. That right there made it infeasible to keep 5.4.46. I've
> stored my 5.4.33 libc and things are back to normal.
> BTW, I'm using 2.0.35 kernel on a 3.2 Slackware system.
> So, what's the deal? I know there's this big push to move to glibc2,
> but this isn't the way to do it ;-) Libc5 *will* be around for quite a
> while, weither the C-Library pundants want it to or not. So would the
> maintainer please give us a clue as to how to track this one down?
>
> > I had to reboot off of floppies and restore the libc.so.5 link to my
> > older library. Anyone know what the story is? Did I botch something?
>
> Check the permissions on the file; make sure it's at least 555
>
> > Barry
>
> --
> Peter A. Castro (doctor@fruitbat.org) or (pcastro@us.oracle.com)
Pete,
upgrade make to 3.77 to cure that.
Matthew D. Pitts
N8OHU
mpitts@suite224.net
http://www.suite224.net/~mpitts/
Ain't gonna let no rock out-praise me
Luke 19:40
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/