Re: More glibc 2.1.1 stuff

[Steve Dunham <dunham@cse.msu.edu>]

Ben Collins <bcollins@debian.org> writes:

> On Fri, Apr 16, 1999 at 11:51:28PM -0700, Stephen Zander wrote:
> > >>>>> "Ben" == Ben Collins <bcollins@debian.org> writes:
> >     Ben> Ok, I've recompiled glibc 2.1.1 with a cvs checkout from
> >     Ben> today. Seems to work pretty well on my ultra. The problems
> >     Ben> that you and I experienced have gone away (apt-get works
> >     Ben> again). Now I just need some kind and brave soul to test it
> >     Ben> on a sun4m :)

> > Well, that was special.  Your package locks my SS5 170MHz solid on
> > reboot.  init loads but never gets off the ground.  BTW, this was on a
> > completely up-to-date unstable system.

> Scratch that. I did use the vfork patch on that last compile, which
> really sucks that it didn't work.

Well vfork() is broken in many of the kernels (except for very recent
CVS kernels).  The "2.1" source that we had a while back had a file
somewhere in sysdeps that short circuited "vfork()" to "fork()" on the
sparc.

I'm installing slink on my SS20, I have a 2.2.5 cvs kernel for sparc32
that I can try on it. (I've put the kernel in my web dir on master, in
case you want to experiment with it.)

> I'm wondering if this is actually a problem with compiling on a sun4u.
> I don't see it as likely, but it's the only other thing I can think of
> (and yes, I am using sparc32 kernel headers and not sparc64).

Shouldn't be a problem - the libraries in slink were compiled on an
Ultra5.  (As long as you make sure you tell it "sparc-linux" on the
./configure line, there should be no problems.)

Also - I've never had the init locking syndrome on my SS20 - I've had
lock ups during the boot sequence, but never init itself.  What kernel
is Stephen running?


Steve
dunham@cse.msu.edu