Re: Restart jhalfs fails
| Newsgroups | gmane.linux.lfs.automated |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 2023-09-12 at 13:44 +0200, Dragan wrote: > > > > On 12/09/2023 13:11, Pierre Labastie ([email protected] via alfs- > discuss Mailing List) wrote: > > > Hmm, once mk_SUDO is done, kernel virtual filesystems are supposed to be > > mounted. I think I'll make a ticket, because this is a defect: kernel vfs > > should > > be checked and remounted if not already mounted when running any part of > > the > > mk_CHROOT or any following mk_XX > > > > Meanwhile, just do "make -C <builddir>/jhalfs devices" if the kernel vfs > > are not > > mounted, before running "make -C <builddir>/jhalfs" (<buildir> is where lfs > > is > > built, usually /mnt/lfs; or change to <builddir>/jhalfs, and omit the "-C > > <builddir>/..." option). > > > > Pierre > > > > Thanks. > > Maybe you can add another check! When jhalfs starts source files (when > existing) were copied to /<builddir/sources> and any missing/new file > downloaded. By restart action is repeated! This is not necessary. > This behavior can be avoided by not ticking "Retrieve source files". I don't think it is good to do this automatically (and actually, the script checks whether the file is already present before downloading it again). But as said, for restarting a build, it is much better to run make in the <builddir>/jhalfs directory (whether changing to it or passing -C to make). Pierre -- http://lists.linuxfromscratch.org/sympa/info/alfs-discuss Unsubscribe: See the above information page