From owner-freebsd-current@FreeBSD.ORG Tue Jul 29 05:01:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A23137B408 for ; Tue, 29 Jul 2003 05:01:53 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECE3943FA3 for ; Tue, 29 Jul 2003 05:01:45 -0700 (PDT) (envelope-from ru@sunbay.com) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h6TC170U022500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jul 2003 15:01:07 +0300 (EEST) (envelope-from ru@sunbay.com) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h6TC15lN022495; Tue, 29 Jul 2003 15:01:05 +0300 (EEST) (envelope-from ru) Date: Tue, 29 Jul 2003 15:01:05 +0300 From: Ruslan Ermilov To: John Message-ID: <20030729120105.GB20737@sunbay.com> References: <20030729103054.GA33488@BSDWins.Com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <20030729103054.GA33488@BSDWins.Com> User-Agent: Mutt/1.5.4i cc: current@FreeBSD.org Subject: Re: -current 'make release' status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2003 12:01:53 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 29, 2003 at 06:30:54AM -0400, John wrote: > Hi, >=20 > I'm currently down to this patch to allow a make release to complete > for -current: >=20 [...] Try setting the KERNEL_FLAGS=3D-DNO_WERROR instead. > without it, the following causes BOOTMFS to abort: >=20 > cc -c -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototy= pes -Wmissing-prototypes -Wpointer-arith=20 > -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -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/co= ntrib/dev/ath -I/usr/src/sys/contrib/dev/a > th/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=3D1= 5000 -mno-align-long-strings -mpreferred-st > ack-boundary=3D2 -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 wi= ll break strict-aliasing rules > /usr/src/sys/sys/buf.h:289: warning: dereferencing type-punned pointer wi= ll 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 wi= ll break strict-aliasing rules > /usr/src/sys/sys/buf.h:310: warning: dereferencing type-punned pointer wi= ll 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 wi= ll break strict-aliasing rules > /usr/src/sys/sys/buf.h:325: warning: dereferencing type-punned pointer wi= ll 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 wi= ll break strict-aliasing rules > /usr/src/sys/sys/buf.h:350: warning: dereferencing type-punned pointer wi= ll break strict-aliasing rules > /usr/src/sys/sys/buf.h:352: warning: dereferencing type-punned pointer wi= ll break strict-aliasing rules > /usr/src/sys/sys/buf.h:352: warning: dereferencing type-punned pointer wi= ll 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 poi= nter will break strict-aliasing rules > . > . > . >=20 > Thoughts? Plans? >=20 > 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: >=20 > chroot $RDIR /bin/sh > /mk doMFSKERN >=20 > works correctly. The 'make release' environment is setup differently > from that of /mk. Depending on what folks think, maybe some form of: >=20 > make mk TARGET=3DdoMFSKERN >=20 > would be appropriate to guarentee consistancy. Just a thought. >=20 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, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/JmIBUkv4P6juNwoRAnDJAJ4jZ7E4vN0/8kFlIbRtrBIKhl6bRgCcCJPH oTjLiO3JEG99m9XDWQHjPNI= =P/M9 -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW--