> Probably help to include errors and problems you were seeing.

config built out of current and the a make produces:

cc1: warnings being treated as errors
In file included from ../../../../sys/systm.h:305,
                 from param.c:48:
../../../../lib/libkern/libkern.h:158: warning: conflicting types for
built-in function `memcmp'
../../../../lib/libkern/libkern.h:159: warning: conflicting types for
built-in function `memcpy'
../../../../lib/libkern/libkern.h:161: warning: conflicting types for
built-in function `memset'
*** Error code 1


and:

qique.nas.nasa.gov > cc -v
Using builtin specs.
gcc version egcs-2.91.60 19981201 (egcs-1.1.1 release)

Now, before I attempt to upgrade the toolchain, I thought would like to
ask the folks who might do this stuff right now what the scoop is.

I upgrade an alpha (which was a ticklish thing in and of itself) and the
compiler for *that* platform is:

poseur > cc -v
Using builtin specs.
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)


I suppose I could ask tech-toolchain, etc., but this is a sparc specific
question.




> Otherwise--is the computer turned on?  ;)

As much as it ever is...

> 
> On Tue, 12 Oct 1999, Matthew Jacob wrote:
> 
> > 
> > { I've tried to resubscribe to this list, but it hasn't happened yet, so
> > please respond to me if it suits you... }
> > 
> > I've installed NetBSD 1.4.1 for sparc, but this won't build a GENERIC
> > kernel out of -current sources. Is the the comp.tar.gz snapshot on
> > ftp.netbsd.org appropriate for building kernels? I fooled around with
> > trying to bootstrap myself from 1.4 to -current last week and had a bad
> > time of it (seems that a  switch to ELF is happening?)
> > 
> > -matt
> > 
> > 
> > 
> 
> --
> scott@lackluster.net
> http://www.lackluster.net/
> 
>                  ~ I had a dream I was a vigilante's sidekick ~
>