As a follow-up to my original message, and I thank the couple people that did respond with suggestions. I seem to have found the issue, which is apparently cvsup17.FreeBSD.org and some file inconsistency.
I was using cvsup17 as it was a very close site hop/ping wise on my various servers, in fact I even ran the cvsup several times against cvsup17 over a couple different days (this has always been fine in the past). Still neither my 7.2 or 6.4 server would compile a kernel without the errors show in my original message. I then changed my cvsup to point to cvsup8.FreeBSD.org, and of course ran a cvsup against the cvsup8 server which did make a batch of updates. After that I then attempted to build a kernel on both my 7.2 and my 6.4 servers, and bingo it all worked perfectly. So I can only assume from this, something is out of sync and not right with the cvsup17 server, not sure if any others are using cvsup17 and having any issues, but I apparently am. Not sure who this should be reported to, so someone can check on the integrity of cvsup17.. --- Howard Leadmon > -----Original Message----- > From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- > sta...@freebsd.org] On Behalf Of Howard Leadmon > Sent: Monday, October 12, 2009 7:31 AM > To: freebsd-stable@freebsd.org > Subject: Kernel Build Issues with latest cvsup of both a 7.2 system,and a > 6.4 system.. > > Not sure if I am just having a run of bad luck here, but I have a bunch > of > various free BSD boxen on both 6.4-STABLE, and on 7.2-STABLE. I try and > make it a point to do a cvsup and update the machines every month or so to > keep things current and any updates/patches installed. I decided a > couple > days ago, it was again time to do this again. > > > > So I ran cvsup on the machines, and set out to rebuild, first doing a > 'make > buildworld', then a 'make installworld', and finally a 'mergemaster' on > the > servers. That all went well, then time for a kernel update, so I > performed > a 'make buildkernel KERNCONF=GENERIC' to create the new kernel, which is > where things went bad. > > > > > > On my 6.4-STABLE x86 machine, I received the following: > > > > cc -c -O -pipe -march=pentium4 -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. > -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath > -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/em > -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 /usr/src/sys/kern/kern_event.c > > /usr/src/sys/kern/kern_event.c:408: warning: no previous prototype for > 'knote_fork' > > *** Error code 1 > > > > Stop in /usr/obj/usr/src/sys/GENERIC. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > > > > > > > On my 7.2-STABLE amd64 machine, I received the following: > > > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona > -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath > -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm > -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD > -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs > -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb - > D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 > --param inline-unit-growth=100 --param large-function-growth=1000 > -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx > -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > /usr/src/sys/amd64/amd64/genassym.c > > In file included from /usr/src/sys/vm/pmap.h:82, > > from /usr/src/sys/amd64/amd64/genassym.c:61: > > ./machine/pmap.h:323: error: expected declaration specifiers or '...' > before > 'vm_memattr_t' > > *** Error code 1 > > > > Stop in /usr/obj/usr/src/sys/GENERIC. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > > > > > > > I have rebuilt the above servers many times over, and I must say it's > worked > great, so was really thrown that not only one version on a server would > blow > up, but two different versions of the OS would pop at the same moment. > Needless to say I haven't tried to rebuild any of my other 6.4 or 7.2 > boxen > yet, as I want to get the above two attempts sorted out first. > > > > Has something changed I am forgetting to do that is not biting me in the > backside, or has some bug been introduced I am now aware of currently > causing issues?? If anyone can help sort this out, or if you need > additional info, please let me know.. > > > > > > > > --- > > Howard Leadmon > > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
