Subject: Re: Problems with PC164SX and -current
To: Ken Wellsch <firstname.lastname@example.org>
From: Jason Thorpe <email@example.com>
Date: 01/29/2000 17:38:57
On Sat, 29 Jan 2000 16:16:18 -0500 (EST)
Ken Wellsch <firstname.lastname@example.org> wrote:
> The last time I was able to "successfully" build -current on my PC164SX
> was Dec 25th. Since then, when starting with a freshly built kernel (and
> current -current) my "make build" tends to die. Earlier in January it
> would fail with the huge clean in libc (massive argv list) - ending with
> a signal 11 death. So I'd simply return to my old kernel and wait til
> I was home again to try with a newer -current. With a fresh sup from
> Friday (Jan 28) I see the following: with a new GENERIC kernel, as soon
> as the new shared libc is installed, the next command faults with signal
> 11. Lots of commands do (I suspect those relying on shared libc). I
> happened to have an old system image circa last September, and when I
> drop libc.so.12.45 in place, replacing the link to the current 12.54,
> everything appears to work again. What the heck have I done wrong here?
> Did I miss rebuilding some part that has left me in a dead-end state?
> Thanks for any suggestions! -- Ken
I noticed this to, and forgot to send a bug report. Foo.
Anyhow, some of the delinting that was done to malloc.c is bogus, and
causes death on the Alpha.
I'll send a PR about it ASAP.
-- Jason R. Thorpe <email@example.com>