| Newsgroups |
gmane.linux.lfs.automated |
| Message-ID |
<[email protected]> |
On 16/06/2022 15:33, Pierre Labastie ([email protected] via
alfs-discuss Mailing List) wrote:
> On Thu, 2022-06-16 at 14:17 +0200, Dragan wrote:
>> Hi,
>>
>> After I have build and successfully booted in current development
>> version of LFS I have tried jhalfs. I started boot build with all log
>> options and saved .config file for kernel from the latest build. In mean
>> time have Bruce committed new version! So the script has downloaded
>> updated sources files and started build. All was going as hoped for
>> until target 1002 : kernel!
>>
>> I have killed build after more than 500 minutes.
>>
>> Today I have chrooted in build and as usually run defconfig and
>> menuconfig and saved .config in my standard location. Then I have
>> cleaned up pulled jhalfs from git and trued to start build again only to
>> fail on Target 503- linux-headers because of authorization issues.
>>
>> I have checked ownership of /lfs and preexisting source directory. Booth
>> were root:root. Clean up, also user lfs, and try again!
>>
>> Same story. I've cleaned up leaving user lfs and started new clean build
>> up. Same story.
>>
>> In both cases have script inherited sudo rights from previously executed
>> commands! Yesterday build have well asked for sudo password.
>>
>> After remembering that I've cleaned the mess up us user lfs exited shell
>> and started new clean build and sudo pwd was necessary. I have just
>> been asked to supply sudo pwd for second time after 617-ggc-pass2.
>>
>> What, if anything, can be done to solve problem?
> Remove everything in /mnt/lfs (or wherever your lfs system is residing), except
> possibly lost+found, if it exists. If you want to keep the source tarballs, and
> you have not yet done so, create a directory /sources on the host, and archive
> the tarballs there first, before cleaning /mnt/lfs. Then pass /sources to
> "Package Archive Directory" (you need to tick "Retrieve source files).
>
> Pierre
I have just finished building jhalfs. I'm using the following to clean
up lfs system as lfs user:
sudo rm -rv
$LFS/{bin,boot,dev,media,mnt,jhalfs,opt,proc,root,run,sbin,srv,sys,tmp,usr,etc,var,tools,build,home,lib,lib64,log}
$LFS/usr/{bin,lib,sbin}
Sources in lfs are deliberately not removed. The build yesterday was
with sources in /lfs and today without them. I remember that yesterday
script stated that linux tarball was not found /sources nor
/sources/sources and have downloaded them (updated files from latest
release).
I have brought VM down after finishing previous build and booted in
build system. After that I have pulled jhalfs and started build.
Below can you se difference in kernel build time!!!!
Besides that I have noticed strong deviations in SBU build time with SBU
at max 21s with -j16 and 1min 15sec based on binutils standard and 73
sec as reported by jhalfs.
------------------------------------------------------
--------------------------------------------------------------------------------
Building target 1002-kernel
[+++++++++++++++++++++++++++++++++\ ] 1 min.
33 sec
Target 1002-kernel OK
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Building target create-sbu_du-report
/lfs/jhalfs/logs /lfs/jhalfs
Using binutils-pass1-2.38 to obtain the SBU unit value.
/lfs/jhalfs
The SBU unit value is equal to 73 seconds at -j16.
The report file r11.1-135-SBU_DU-2022-06-16.report has been created
Please send the /lfs/jhalfs/r11.1-135-SBU_DU-2022-06-16.report
file to [email protected]
That will help us to keep more accurate SBU and
disk usage values into the book. Thanks.
--------------------------------------------------------------------------------
umount: /lfs/dev/pts unmounted
umount: /lfs/dev unmounted
umount: /lfs/run unmounted
umount: /lfs/proc unmounted
umount: /lfs/sys unmounted
--------------------------------------------------------------------------------
Finished the build of r11.1-135
--------------------------------------------------------------------------------
W A R N I N G
--------------------------------------------------------------------------------
To be able to boot your new system you need to follow
the next steps:
- Mount the virtual kernel file systems.
- Enter to the chroot using the command found
in the section -Entering the Chroot Environment-
except if building with METHOD=boot.
- Set a password for the root user.
- Edit or create /etc/fstab and any other configuration file
required to suit your needs.
- Set-up the boot loader.
You can set-up the new boot-loader installed on the new system
or the host bootloader.
If the last, it is better to exit first from the chroot.
- Exit from the chroot and umount the filesystems.
If you are an experienced LFS user, several of those steps can be
skipped or done in a different way. But then, that is something
that you already know and there is no need to discuss it here.
--------------------------------------------------------------------------------
Have a nice day :-)
--------------------------------------------------------------------------------
make[1]: Leaving directory '/lfs/jhalfs'
done
<jhalfs> exit
<jhalfs> exit
draak@draak-VirtualBox:~/jhalfs$
--
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page