Unfortunately, pulling up /bin/sh and usr.bin/printf sources
result in the same solid problem.

Can any one give me a quick advise, how to modify the makefile to 
build sh with debug info?
The sh used seams to be an ash.
And my SS4 seems to be the right machine to lock for that problem. sig.


As a work around an sh for a 1.6.2 Distribution can be used.
But also libtool seems to suffer. (Only now and than)
  
On Tue, Feb 22, 2005 at 05:55:46PM +0100, Andreas Hallmann wrote:
> Martin Husemann wrote:
> 
> >On Tue, Feb 22, 2005 at 09:34:51AM +0100, Andreas Hallmann wrote:
> > 
> >
> >>Resulting sets are working perfectly on a turbo sparc based system, 
> >>where as sh is dumping core
> >>on a micro sparc II based SS4-110.
> >>   
> >>
> >
> >There was a sh bug recently fixed in:
> > $NetBSD: expand.c,v 1.68 2005/02/14 20:46:26 dsl Exp $ 
> >This was triggered by random stack content, but I haven't seen it core
> >dump.
> > 
> >
> 
> Thanks. Thats it. It replaced /bin/sh with a version from 1.6.2 and now 
> I'm back in business.
> While trying to find a minimum pull up set for /bin/sh, my SS4 is 
> happily doing a make world.
> 
> For the moment it seems that beside pulling up /bin/sh, pulling up 
> /usr/bin/sh is also necessary.


Last think was wrong. pulling up usr.bin/printf was needed.


> 
> >I've been running supersparc and v8 optimized builds on my Krups and LX
> >for years, and never seen any problems like you describe.
> >
> >Martin
> >
> > 
> >
> Krups, hmm, true color, seems to be a great x-terminal -- right?
> 
> Andreas
> 

-- 
NetBSD: If you happen to have any problem with your uptime.