Date: Tue, 29 Jul 2003 17:38:48 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John De Boskey <jwd@bsdwins.com> Cc: Peter Wemm <peter@FreeBSD.org> Subject: Re: -current 'make release' status? [SOLVED] Message-ID: <20030729143848.GA37496@sunbay.com> In-Reply-To: <20030729134154.GA7048@BSDWins.Com> References: <20030729103054.GA33488@BSDWins.Com> <20030729120105.GB20737@sunbay.com> <20030729123740.GA6239@BSDWins.Com> <20030729125738.GA27879@sunbay.com> <20030729134154.GA7048@BSDWins.Com>
next in thread | previous in thread | raw e-mail | index | archive | help
--BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 29, 2003 at 09:41:54AM -0400, John De Boskey wrote: > ----- Ruslan Ermilov's Original Message ----- > > >=20 > > > No, I have nothing in my environment that should affect the > > > build, no /etc/make.conf in the chroot area.. > > >=20 > > But then again: running "make rerelease" is effectively just > > calls the command above. I'm currently in the middle of the > > "make release" and will see if this is reproduceable. > >=20 > > > # chroot /vol/vol0/work/5-current-chrootdir /bin/sh > > > # env > > >=20 > > > A few things not needed that are inherited from my normal > > > account, but nothing that should have a negative affect. > > >=20 > > Do you still get the error if you try "make rerelease"? > > Do you still get the error if you try "chroot ... /mk"? > > Do you still get the error if you try "env -i chroot ... /mk"? >=20 > I'll see what I can find.. >=20 John, I see the same breakage as you do. But in all three cases above, I see the same breakage (as expected). Even if I'm running "chroot /data/ru/R" then "./mk doMFSKERN", I still get it: : 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 : ... : *** Error code 1 :=20 : Stop in /usr/obj/usr/src/sys/BOOTMFS. Forget what I've said about NO_WERROR, it (unfortunately) only applies to the userland. Still, running "make rerelease KERNEL_FLAGS=3DWERROR=3D" gets the release done. I wondered why I get it, and similarly my nigthly "buildkernel" completed without errors. This turned out to be due to the -O vs. -Os differences. For example, compiling vfs_subr.o =66rom the GENERIC kernel results in these same warnings when compiled with COPTFLAGS=3D"-Os -pipe". Peter, should we switch -Werror back off in kern.pre.mk? Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/Job4Ukv4P6juNwoRAvo6AJ4poFDV7bjl/dhhaVmgOuqumXgwwQCcCqzv aZlLdlzD28tvsa3MyoCmWAs= =i/HU -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030729143848.GA37496>