Date: Sat, 8 Jun 2013 15:17:22 -0400 From: Glen Barber <gjb@FreeBSD.org> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-current@FreeBSD.org, Jimmy <jimmy.kelley@charter.net> Subject: Re: 10-CURRENT i386 memstick snapshots broken? Message-ID: <20130608191722.GE13292@glenbarber.us> In-Reply-To: <926EF579-8AC9-4A98-8A81-4E978A627199@kientzle.com> References: <20130607205129.GA1103@jmobile.jimmy.net> <20130607212256.GG38117@glenbarber.us> <20130608173411.GD13292@glenbarber.us> <926EF579-8AC9-4A98-8A81-4E978A627199@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nHwqXXcoX0o6fKCv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote: >=20 > On Jun 8, 2013, at 10:34 AM, Glen Barber wrote: >=20 > > 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? > >>>=20 > >>=20 > >> Hmm. Thanks for the report. I'll take a look at the logs for i386, b= ut > >> they are generated the same way as the amd64, so in theory should not > >> have any noticable difference. > >>=20 > >=20 > > 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. > >=20 > > The scripts chroot into the scratch directories, and run the "real" > > release builds. >=20 > Have you tried using Crochet for this sort of thing? >=20 > Since it was designed from the ground up for cross-building > bootable images, it should avoid these issues. >=20 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. >=20 >=20 Yes, I have this same issue with sparc64. Glen --nHwqXXcoX0o6fKCv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRs4NCAAoJEFJPDDeguUajNKYIAIiNcG0s9hRWbI04+X9hAehZ TC31z+xwRT9Iko0Y+/VPlxu9UW20xtWSAA+Q7+E9QoemC8JlIFSfK+N9QD7lQ/NB CnQ7ybNnGDMCCw0b3IrOFhXMIqF4vo0DuIjdlWB/XnP9It1LmMWQNPfKlLwpX3ka RLwlMvV4q5bgHV1/fV0zr4uod/+kDlKcQ/Ffky8E0zx8rmQCq6PBcCubu20HE2E2 TUyJU6GywLDgeAToPhjxYCZGYIxai1GoPL/SeGIvWV8Dm3Vxr7CQ2dH8X8vfipZ/ 9hxMa5+7U+Ct2YLpAu7DqmRTcckc3RTdPqWfRdB4KdiupI76EZfn25XhzSfrnHA= =cKG2 -----END PGP SIGNATURE----- --nHwqXXcoX0o6fKCv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130608191722.GE13292>