10-CURRENT i386 memstick snapshots broken?
hrs at FreeBSD.org
Sat Jun 8 20:04:48 UTC 2013
Tim Kientzle <tim at kientzle.com> wrote
in <926EF579-8AC9-4A98-8A81-4E978A627199 at kientzle.com>:
ti> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
ti> > On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
ti> >>> Has anyone else tried the i386 memstick and having the same problem?
ti> >> Hmm. Thanks for the report. I'll take a look at the logs for i386, but
ti> >> they are generated the same way as the amd64, so in theory should not
ti> >> have any noticable difference.
ti> > For amd64 and i386, native binaries are built, and installed into
ti> > scratch directories; for powerpc and powerpc64, I just use the amd64
ti> > binaries, because I cannot directly use the chroot binaries for
ti> > non-native architecture.
ti> > The scripts chroot into the scratch directories, and run the "real"
ti> > release builds.
ti> Have you tried using Crochet for this sort of thing?
ti> Since it was designed from the ground up for cross-building
ti> bootable images, it should avoid these issues.
ti> The only fundamental limit right now is that Crochet uses
ti> the host system to build the UFS filesystems, so it can't
ti> build big-endian MIPS images on i386, for example.
makefs does not work? It can build BE FFS images on LE platforms.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
More information about the freebsd-current