Date: Tue, 29 Jul 2003 15:01:05 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John <jwd@bsdwins.com> Cc: current@FreeBSD.org Subject: Re: -current 'make release' status? Message-ID: <20030729120105.GB20737@sunbay.com> In-Reply-To: <20030729103054.GA33488@BSDWins.Com> References: <20030729103054.GA33488@BSDWins.Com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Tue, Jul 29, 2003 at 06:30:54AM -0400, John wrote:
> Hi,
>
> I'm currently down to this patch to allow a make release to complete
> for -current:
>
[...]
Try setting the KERNEL_FLAGS=-DNO_WERROR instead.
> without it, the following causes BOOTMFS to abort:
>
> cc -c -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
> -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src
> /sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/a
> th/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -mno-align-long-strings -mpreferred-st
> ack-boundary=2 -ffreestanding -Werror /usr/src/sys/cam/cam_periph.c
> In file included from /usr/src/sys/cam/cam_periph.c:41:
> /usr/src/sys/sys/buf.h: In function `BUF_LOCK':
> /usr/src/sys/sys/buf.h:289: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h:289: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h: In function `BUF_TIMELOCK':
> /usr/src/sys/sys/buf.h:310: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h:310: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h: In function `BUF_UNLOCK':
> /usr/src/sys/sys/buf.h:325: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h:325: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h: In function `BUF_KERNPROC':
> /usr/src/sys/sys/buf.h:350: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h:350: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h:352: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/sys/buf.h:352: warning: dereferencing type-punned pointer will break strict-aliasing rules
> /usr/src/sys/cam/cam_periph.c: In function `cam_periph_mapmem':
> /usr/src/sys/cam/cam_periph.c:624: warning: dereferencing type-punned pointer will break strict-aliasing rules
> .
> .
> .
>
> Thoughts? Plans?
>
> It's also worth noting that the BOOTMFS kernel build is inconsistant. The
> initial build via 'make release' fails with no patch. After the failure,
> a followup:
>
> chroot $RDIR /bin/sh
> /mk doMFSKERN
>
> works correctly. The 'make release' environment is setup differently
> from that of /mk. Depending on what folks think, maybe some form of:
>
> make mk TARGET=doMFSKERN
>
> would be appropriate to guarentee consistancy. Just a thought.
>
If this is the case, then it's a bug and should be fixed. I am
looking to see now if I can reproduce the problem, but a wild
guess is that: release/Makefile calls chroot(8) a bit differently,
with a clean environment, like this:
env -i /usr/sbin/chroot ${CHROOTDIR} /mk
Could it be that you have something in your environment similar
to NO_WERROR?
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software Ltd,
ru@FreeBSD.org FreeBSD committer
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE/JmIBUkv4P6juNwoRAnDJAJ4jZ7E4vN0/8kFlIbRtrBIKhl6bRgCcCJPH
oTjLiO3JEG99m9XDWQHjPNI=
=P/M9
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030729120105.GB20737>