From owner-freebsd-current@FreeBSD.ORG Sat Jun 8 19:10:31 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4593883E; Sat, 8 Jun 2013 19:10:31 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 07D94108D; Sat, 8 Jun 2013 19:10:30 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r58JAMRW004768; Sat, 8 Jun 2013 19:10:22 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.123] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id mjkr3tmxjtikfke72xp965exgi; Sat, 08 Jun 2013 19:10:22 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: 10-CURRENT i386 memstick snapshots broken? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/signed; boundary="Apple-Mail=_76E211BB-0E11-42DD-9CDC-A4CACE3BEEB3"; protocol="application/pgp-signature"; micalg=pgp-sha1 From: Tim Kientzle In-Reply-To: <20130608173411.GD13292@glenbarber.us> Date: Sat, 8 Jun 2013 12:10:16 -0700 Message-Id: <926EF579-8AC9-4A98-8A81-4E978A627199@kientzle.com> References: <20130607205129.GA1103@jmobile.jimmy.net> <20130607212256.GG38117@glenbarber.us> <20130608173411.GD13292@glenbarber.us> To: Glen Barber X-Mailer: Apple Mail (2.1283) Cc: freebsd-current@FreeBSD.org, Jimmy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 08 Jun 2013 19:10:31 -0000 --Apple-Mail=_76E211BB-0E11-42DD-9CDC-A4CACE3BEEB3 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii 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. 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. Tim --Apple-Mail=_76E211BB-0E11-42DD-9CDC-A4CACE3BEEB3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) iQEcBAEBAgAGBQJRs4GcAAoJEGMNyGo0rfFB2OIH/3HGxS9bCbRrw0CTdpUuwWKv tvrR0hlLdt9kVWetYFZAeEMlNJHn3xRQIzg5WoOqbNt72lhgeMlDirIiNoxviLNn bRpQ6NGJd9nXAU5N1GXphUyYFIMEWGmF5qCVMcPz4Gv6OyvAMuNdrp/MrFiz9ToD 3HTavZBff5ATxlgbVizsH+D0vvGNJekG+P9XfG43/WA0f8kmLSNGe1Q/HsF2dd1+ NWOuFbhD/Xce09X8x3hjJ8ToBq/NWtdpCbWofVRofBHwhY0h1a1umHQ4uTy+hmq9 9bRMpy8RbsqqBtpr7hvTsq75I1kyqQG3lTSrZzC+gWC0qa5WNtzHkCDie3kfCug= =DHRr -----END PGP SIGNATURE----- --Apple-Mail=_76E211BB-0E11-42DD-9CDC-A4CACE3BEEB3--