Re: libc.so.5.4.46 binaries
doctor@fruitbat.org
Mon, 12 Oct 1998 14:31:28 -0700 (PDT)
Matthew D. Pitts stated ...
> > 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?
> >
> > --
> > Peter A. Castro (doctor@fruitbat.org) or (pcastro@us.oracle.com)
> Pete,
> upgrade make to 3.77 to cure that.
This proved to be the real problem. I've had several people comment
that I should have read the release notes. Indeed, I would have, had
there been any with the distribution I pulled. I just check the place I
pulled it from and, if by magic, the release notes are where I would have
expected them to be the first time. Perhaps I just missed a mirror
refresh. Anyway, thanks to those who took the time to comment to me.
> Matthew D. Pitts
> N8OHU
> mpitts@suite224.net
> http://www.suite224.net/~mpitts/
> Ain't gonna let no rock out-praise me
> Luke 19:40
--
Peter A. Castro (doctor@fruitbat.org) or (pcastro@us.oracle.com)
-
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/