Hi. I'm building a basic system with xorg. Two questions: 1. when one resumes a build does it start from the failure/stoppage or does it delete the existing? 2. Can anyone tell me if there is a 'order of build' file for the project? Something that maybe can be edited. Thanks Cliff

If it fails in configure, you can just run the configure script again. But if it fails in make, you should never resume the build. The results of doing so are quite unpredictable. Delete the old files with "make clean" and then run make again.

The various Makefiles in different directories can show you the order in which things get built, but they are difficult to read and not editable in practice.

Thanks Hazel. When I said resume the build I meant the whole build of an Ayralinux. Does it resume from where there was a stoppage or an error or does it start again? I'm thinking I could correct an error then resume. Cliff

I don't know what are you trying to build. The general answer is: it depends on the actual build system. If it was good enough it can continue where is was stopped last time. Otherwise it can repeat steps (unnecessarily) or skip required parts. This is all about quality. If it was not good enough you need to restart it from the beginning again and again to avoid problems.

The order of builds (or build dependency chain/tree) is specified in the build environment and the quality of the build system highly depends on the perfection of that dependency tree.

Right. I'm using the Ayralinux builder disk to build an lfs system with xorg. The build is failing at the infamous cdrtools. Why it's installing that at this stage I don't know. . Thanks again Cliff

Right I've cured the cdrtool problem. I managed to edit the 'build log' and then install the package manually. Anyway starting Stage 5 I get another error following the admin-user install

Starting stage 5
umount: /mnt/lfs/dev/pts: no mount point specified.
umount: /mnt/lfs/dev/shm: no mount point specified.
umount: /mnt/lfs/dev: not mounted.
umount: /mnt/lfs/sys: not mounted.
umount: /mnt/lfs/proc: not mounted.
umount: /mnt/lfs/run: not mounted.
mount: /dev bound on /mnt/lfs/dev.
mount: devpts mounted on /mnt/lfs/dev/pts.
mount: proc mounted on /mnt/lfs/proc.
mount: sysfs mounted on /mnt/lfs/sys.
mount: tmpfs mounted on /mnt/lfs/run.
mount: tmpfs mounted on /mnt/lfs/dev/shm.
mount: /mnt/lfs/dev: mount point does not exist.
mount: /mnt/lfs/dev/pts: mount point does not exist.
mount: /mnt/lfs/proc: mount point does not exist.
mount: /mnt/lfs/sys: mount point does not exist.
mount: /mnt/lfs/run: mount point does not exist.
mount: /mnt/lfs/dev/shm: mount point does not exist.
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
Traceback (most recent call last):
File "./build-arya", line 335, in <module>
freshBuild(stage)
File "./build-arya", line 201, in freshBuild
if getParamValue('CREATE_BACKUPS') == 'y' or getParamValue('CREATE_BACKUPS') == 'Y':
File "./build-arya", line 72, in getParamValue
with open(propsFile) as f:
IOError: [Errno 2] No such file or directory: 'build-properties'

What is happening here? i assume this is the chroot script?

thanks Cliff