Re: LFS build of File-5.45 problem stops on compilation of seccomp.c
"Pocket" ([email protected] via lfs-support Mailing List) <[email protected]> Thu, 20 Feb 2025 10:50:52 -0500
| Newsgroups | gmane.linux.lfs.support |
|---|---|
| Message-ID | <[email protected]> |
On 2/20/25 10:25 AM, dave kohler ([email protected] via lfs-support Mailing List) wrote: > This morning I noticed something that has changed to my Arch build > environment that might be related to this problem. I would like your > feedback on whether the info below is an environmental problem for me. > -------- > This morning I did the routine invocation of pacman -Syyu to get updates > from the Arch repositories. > While pacman processed the updates it spit out two warnings about > transitions in some of the directories. > I unfortunately do not have those messages at the moment but I have > fetched a few lines from near the tail of the pacman.log file. > When I use archlinux for a host system I always create a systemd-nspawn container which I boot to. It keeps me from having a RUD of the host system. https://wiki.archlinux.org/title/Systemd-nspawn Add devtools into the container and you should be ready to build after sudo systemd-nspawn -b -D <path/to/Container> The other way is: https://wiki.archlinux.org/title/Chroot If you are rebuilding or building packages: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot -- Hindi madali ang maging ako -- http://lists.linuxfromscratch.org/sympa/info/lfs-support Unsubscribe: See the above information page