[Aboriginal] lfs-bootstrap in control-images-1.1.0 incompatible with aboriginal-1.4

Rob Landley rob at landley.net
Sun Apr 19 16:56:52 PDT 2015

On Sun, Apr 19, 2015 at 10:38 AM, Alan Post <alanpost at sunflowerriver.org> wrote:
> Hello Rob,
> We last spoke in March 2011.  I submitted a typo patch prepared while reading
> documentation.  I have another issue to report.
> A source compile of lfs-bootstrap build from control-images-1.1.0 does not
> work using aboriginal-1.4, as it is missing changeset 39:31d7462a8649[1].

Yes, that's why I checked in a change and updated the prebuilt binaries:

> This causes the build to run in the root filesystem, which runs out of
> disk space, creating errors like this:

I noticed. The previous build had the assumption that it was either
running via dev-environment.sh in a qemu squashfs, or via
more/chroot-splice.sh in a chroot. It used "can I write to /.testfile"
to distinguish, which wasn't a good test for tmpfs' "root is writeable
but doesn't have much free space".

> Applying changeset 39:31d7462a8649 causes lfs-bootstrap to build.
> The binary lfs-bootstrap[2] also works.
> Any chance of cutting a new control-images?  This was a real head
> scratcher until I started spelunking inside your binary release
> and found the cause.

Happy to. What does "cutting" mean in this context, adding a mercurial
tag? (I thought the binary images were up to date, their timestamp
says last month. Did I rebuilt them wrong?)

(I need to do a new lfs-bootstrap based on something more current, maybe 7.4.)


More information about the Aboriginal mailing list