6.1 PRERELEASE kernel build error

[Casey Scott]

----- Original Message -----
From: Kris Kennaway <kris at obsecurity.org>
To: Casey Scott <casey at phantombsd.org>
Cc: Kris Kennaway <kris at obsecurity.org>, freebsd-stable at freebsd.org
Sent: Thursday, March 23, 2006 10:48:29 AM GMT-0800
Subject: Re: 6.1 PRERELEASE kernel build error

On Thu, Mar 23, 2006 at 10:43:59AM -0800, Casey Scott wrote:
> 
> ----- Original Message -----
> From: Kris Kennaway <kris at obsecurity.org>
> To: Casey Scott <casey at phantombsd.org>
> Cc: freebsd-stable at freebsd.org, Kris Kennaway <kris at obsecurity.org>
> Sent: Thursday, March 23, 2006 10:20:02 AM GMT-0800
> Subject: Re: 6.1 PRERELEASE kernel build error
> 
> On Thu, Mar 23, 2006 at 08:25:35AM -0800, Casey Scott wrote:
> > 
> > ----- Original Message -----
> > From: Kris Kennaway <kris at obsecurity.org>
> > To: Casey Scott <casey at phantombsd.org>
> > Cc: freebsd-stable at freebsd.org
> > Sent: Thursday, March 23, 2006 0:27:30 AM GMT-0800
> > Subject: Re: 6.1 PRERELEASE kernel build error
> > 
> > On Wed, Mar 22, 2006 at 10:27:56AM -0800, Casey Scott wrote:
> > > I just upgraded 5.4 stable to 6.1 PRERELEASE via buildworld. I am trying to build a kernel, and keep getting this error at "make".
> > > 
> > > 
> > > ......
> > > cc -c -O2 -pipe -fno-strict-aliasing -march=pentium4 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -std=c99  -nostdinc -I-  -I. -I../../.. -I../../../contrib/altq -I../../../contrib/ipfilter -I../../../contrib/pf -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd -I../../../contrib/ngatm -I../../../dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000  -mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror  ../../../fs/devfs/devfs_vnops.c
> > > ../../../fs/devfs/devfs_vnops.c:1172: warning: redundant redeclaration of 'devfs_ops_f'
> > > ../../../fs/devfs/devfs_vnops.c:70: warning: previous declaration of 'devfs_ops_f' was here
> > > ../../../fs/devfs/devfs_vnops.c:1183: warning: redundant redeclaration of 'devfs_vnodeops'
> > > ../../../fs/devfs/devfs_vnops.c:68: warning: previous declaration of 'devfs_vnodeops' was here
> > > ../../../fs/devfs/devfs_vnops.c:1205: warning: redundant redeclaration of 'devfs_specops'
> > > ../../../fs/devfs/devfs_vnops.c:69: warning: previous declaration of 'devfs_specops' was here
> > > *** Error code 1
> > > 
> > > 
> > > I even get that error building a kernel from the GENERIC config. I think something is wonky with gcc. >Has anyone else seen this, or know what could be causing it?
> > >
> > >You didn't follow the correct upgrade order - it's documented in the
> > >handbook and in /usr/src/UPDATING.
> > >
> > >Kris
> > 
> >
> > Thanks for that info. I have the kernel built now. I noticed that it
> > is built from the source in /usr/obj and not /usr/src.
> >
> >No, /usr/obj contains the results of your buildworld, it's not a
> >second copy of the source.
> >
> > In 6.x, do we
> > have to keep /usr/obj after installworld, or should installworld
> > have updated /usr/src ?
> 
> >You do not have to keep /usr/obj.
> >
> >Kris
> >
> >P.S. Please wrap your lines so that your emails may be easily read.
> 
> 
> That's what I thought. However, when I  rm -rf /usr/obj/, and try 
> to build the kernel again, I can the same error that I mentioned
> at the beginning of the thread. If I buildworld again, and do a 
> make buildkernel KERNCONF=XXX, the build succeeds.
>
>Yes, because you removed it in the middle of your upgrade.  According
>to the directions, installworld comes late in the sequence.
>
>Kris

Sorry, I should have been more clear. I have already performed the 
entire procedure specified in updating. The system is running the 
new 6.1 binaries/kernel.

After booting into the new environment, I removed /usr/obj. 
At /usr/src, I did  make buildkernel KERNCONF=XXX, and received the
error in question. Upon doing another buildworld, the buildkernel 
succeeded.

Casey