Date: Sat, 8 Jun 2013 20:43:35 -0400 From: Glen Barber <gjb@FreeBSD.org> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: freebsd-current@FreeBSD.org, Jimmy <jimmy.kelley@charter.net> Subject: Re: 10-CURRENT i386 memstick snapshots broken? Message-ID: <20130609004335.GF13292@glenbarber.us> In-Reply-To: <51B38398.8030509@freebsd.org> References: <20130607205129.GA1103@jmobile.jimmy.net> <20130607212256.GG38117@glenbarber.us> <20130608173411.GD13292@glenbarber.us> <926EF579-8AC9-4A98-8A81-4E978A627199@kientzle.com> <20130608191722.GE13292@glenbarber.us> <51B38398.8030509@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--qftxBdZWiueWNAVY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 08, 2013 at 02:18:48PM -0500, Nathan Whitehorn wrote: > On 06/08/13 14:17, Glen Barber wrote: > > On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote: > >> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote: > >> > >>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote: > >>>>> Has anyone else tried the i386 memstick and having the same problem? > >>>>> > >>>> Hmm. Thanks for the report. I'll take a look at the logs for i386,= but > >>>> they are generated the same way as the amd64, so in theory should not > >>>> have any noticable difference. > >>>> > >>> For amd64 and i386, native binaries are built, and installed into > >>> scratch directories; for powerpc and powerpc64, I just use the amd64 > >>> binaries, because I cannot directly use the chroot binaries for > >>> non-native architecture. > >>> > >>> The scripts chroot into the scratch directories, and run the "real" > >>> release builds. > >> Have you tried using Crochet for this sort of thing? > >> > >> Since it was designed from the ground up for cross-building > >> bootable images, it should avoid these issues. > >> > > I have not, primarily because I was not aware of crochet when > > I originally started this. Although, by using the release stuff from > > the base system, we do get a weekly run-test of the 'make release' bits > > in head/ and stable/9/, so in theory, there would be no surprises when > > it is -RELEASE time. > > > >> The only fundamental limit right now is that Crochet uses > >> the host system to build the UFS filesystems, so it can't > >> build big-endian MIPS images on i386, for example. > >> > >> > > Yes, I have this same issue with sparc64. > > >=20 > Why not use makefs? It can build cross-endian UFS images. The scripts do (as far as I recall for sparc64) use makefs, but a port is needed to create the sparc-capable ISO image. Glen --qftxBdZWiueWNAVY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRs8+3AAoJEFJPDDeguUajSm0H/1LsLpUOz2V+Hdd9Ts/XZGya uZi/HJ8fomH8iUf7/YSM2RJNmhh70l4ilI+c4iB4d0kKNAOJAq95gX8LFJh0MUxm euZnHaPWNNZZSakljyS/+dasMf0KVOZoN0yOmvqQzXGEEY4cizKdLoNnt1s62jtO 6JLuVDhpdJD9jjevWrME+chYMTS4eWSz/4lBqIZ3w+zmW4F6E/U8LHo9ma6twVKg FgV+TXJsRpVamPOIi0ZoIVdSRGSQRU0xrI/+tbPSg190fGZ4FDX/Wmtzx3IAurqi BasOHL5CASI+ksWMV2xlYuWTT8xWckGjVXrYfeO+tAeCtL4KVY9O3Dc5UhOSNhA= =Z6Uy -----END PGP SIGNATURE----- --qftxBdZWiueWNAVY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130609004335.GF13292>