Date: Wed, 10 Sep 2014 16:44:08 -0700 From: Peter Wemm <peter@wemm.org> To: freebsd-stable@freebsd.org Cc: John Baldwin <jhb@freebsd.org> Subject: Re: cross build for RELENG8 on RELENG10 now fails Message-ID: <9468585.hm97Wx3h1R@overcee.wemm.org> In-Reply-To: <20140910233009.GA56050@ambrisko.com> References: <54107156.4080605@sentex.net> <5978109.GnR6la40iO@ralph.baldwin.cx> <20140910233009.GA56050@ambrisko.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart4238276.VlYqiCrO8P Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Wednesday, September 10, 2014 04:30:09 PM Doug Ambrisko wrote: > On Wed, Sep 10, 2014 at 11:52:09AM -0400, John Baldwin wrote: > | On Wednesday, September 10, 2014 11:42:14 AM Mike Tancsa wrote: > | > When I upgraded our cross build server to RELENG10 from 9, I lost= the > | > ability to build RELENG_8 images. Is there some magic that needs= to be > | > done in order to make this work on RELENG_10 ? > |=20 > | I punted on building 8 on 10 when I ran into this (I know use bhyve= vms > | running 8 to test MFCs to 8 since I can boot-test them as well as > | build-test them). I don't think there are any known workarounds. >=20 > We've been building older releases via chroot and setting environment= > variables. I have some local hacks to set the uname etc info. in > a jail via sysctl in the jail. This is the only "officially" supported cross-branch mode we supported,= aside=20 from=20the N -> N+1 path. It's how we build everything at work, and how we build in the freebsd.o= rg=20 cluster. It's way faster than a VM and generally no hassle. For the freebsd.org cluster: fetch 8.4-REL base.* -> build stage 1 -> svn checkout -> buildworld fro= m 8.4- REL to 8-stable -> installworld in a clean chroot -> roll tarballs. fetch 9.3-REL base.txz -> build stage 1 -> svn checkout -> buildworld f= rom=20 9.3-REL to 9-stable -> installworld in a clean chroot -> roll tarballs.= .. and so on. For 11.x we use a ftp.freebsd.org/snapshots build. At work, we go much, much further. We even build 4-stable, 6-stable an= d 7- stable on 11.x hosts this way. (Why? we modify libc.so.4 to run bette= r on=20 10.x/11.x and copy it from the 4.x build environment into the compat ar= ea on=20 later releases during the build process) But we *never* cross build from head. Too many moving targets, harder = to=20 reproduce a specific build, etc. We used to have this written down somewhere. The supported upgrade pat= h used=20 to be explicitly documented as N.0 -> N-stable-> N+1.0, ie: 5-stable -> 6.0 -> 6-stable -> 7.0 -> 7-stable -> 8.0 -> 8-stable etc, = and=20 never in reverse. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI= 6FJV UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246 --nextPart4238276.VlYqiCrO8P Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABAgAGBQJUEOJNAAoJEDXWlwnsgJ4EKnkH/2UwdWBFE7OjTQB3V3YXkLGH hUB1qinoLm4z5vQwnuL17SlKA0kP1S84lTgSJ5VxcdN8Z/bioxD0WVRLy3wZ5r7X Sq8oaIDX487BX5Da5zN0MMNPc4IGpK82LxPxdWuUEJ4t2pU2oYh4/42D2Y0FZDMN lMA/9aMfA+YPF4N3CIFo9fleUEFttshB7jSfuNO2D/vAFP1KhyGDNmotuHaZ+t1G vOF2WTUPwVesUiNRqXZV5KcBGi4ObVjkju41hpVQ8L8D63WhZz1ZKwv9Ub0z5sSP CKcc52BMyqZVl1/X4B1sGkR41Eck7K1xm1hULrVqw+vQAC8BrBYrUCTEiZxPvQQ= =OOYS -----END PGP SIGNATURE----- --nextPart4238276.VlYqiCrO8P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9468585.hm97Wx3h1R>