Tim Kientzle <t...@kientzle.com> wrote in <926ef579-8ac9-4a98-8a81-4e978a627...@kientzle.com>:
ti> ti> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote: ti> 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> >>> ti> >> 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> >> ti> > 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> > ti> > The scripts chroot into the scratch directories, and run the "real" ti> > release builds. ti> ti> Have you tried using Crochet for this sort of thing? ti> ti> Since it was designed from the ground up for cross-building ti> bootable images, it should avoid these issues. ti> 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. -- Hiroki
pgpSfiguwNi65.pgp
Description: PGP signature
