Subject: Re: previous declaration of `catclose'
To: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
From: Scott J. Ellentuch <tuc@valhalla.stormking.com>
List: port-sun3
Date: 05/22/1995 07:15:18
In der Mouse's own words (And I ">_") :
> 
> > Well, I'm trying to compile the Sun 3 kernel from scratch (Thats a
> > story in and of itself) and I've run into a little problem :
> 
> > # make
> > ===> lib
> > ===> csu
> > ===> m68k
> 
> This looks more like a "make" in /usr/src, which will not build you a
> kernel.
>
	I'd first off like to thank *EVERYONE* for mentioning my COMPLETELY
incorrect statement that I was trying to build the kernel.  I, indeed, was 
trying to re-compile THE ENTIRE RELEASE.
> 
> > ===> c++
> > ===> libarch
> > ===> libc
> > cc -O -DNLS -DYP -DLIBC_SCCS -DSYSLIBC_SCCS -I/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -DFLOATING_POINT  -c /src/lib/libc/nls/catclose.c
> > /src/lib/libc/nls/catclose.c:20: conflicting types for `catclose'
> > /usr/include/nl_types.h:46: previous declaration of `catclose'
    ^^^^^^^^^^^^
>
> > *** Error code 1
> 
> > I'm 'SUP' to the minute...... Where do I go from here?
> 
> Try "make -n build", which will indicate the correct order to rebuild
> things in.  In particular, you should do include files first, libraries
> second, and then the rest of the world; if you're making a big jump,
> you will also need to tweak a couple of other things, such as the
> special-case necessary to rebuild lex if your binary is too old to grok
> the current scan.l (if lex whines about percent signs in scan.l, copy
> initscan.c to scan.c, then "make" / "make install" to install an
> up-to-date lex).
>
	Then what is a "make" trying to do?  Also, according to the 
instructions , isn't my /usr mounted Read Only?  And, while I'm re-building
everything if I decide to do something else, won't my includes be 
incorrect with the version installed? I guess I really never ran into
this since Linux on my PC took an hour or so and I've put 30 into
this and only have about 490 .o's in libc. (NOT blaming the OS, just the
3/50 and possibly Linux NFS).

	I am trying to go from what is in the tarballs to what is currently
SUP'd.  Which buyes me more stability, Kernel or rest of the system? If I
put a new kernel in with the rest of the tarball stuff, will I be better
off than the reverse.  Or can I? (Sometimes if you aren't in sync they don't
play so well)
> 
> 			    mouse@collatz.mcrcim.mcgill.edu
>
						 ^^^^^^MUSIC to my ears.
			Tuc