benvd
commented
2 years ago Every now and then I start working on updating this for the latest LFS version, but I generally don't manage to make it all the way through... :)
That said, I did revisit this for LFS 10 (not 11 though), with pacman 6.0.0, which uses meson. I managed to build and install pacman, and then use pacman to install at least some packages to the final system, but I never completed it, so caveat emptor.
[edit] I realize there's nothing about libxml2 in this explanation, but apparently that never posed a problem on my side...
Stage 1 - Installing pacman to your temporary toolchain
This stage begins right before section 8.3. Man-pages-5.10 of the LFS 10.1 book.
Pacman dependencies
Pacman has a fair amount of dependencies, and some of those in turn have other dependencies. When all is said and done, we'll need to install fourteen packages. Thirteen of these have instructions in either LFS or BLFS that you can follow verbatim:
- zlib
- libarchive
- libcap
- pkg-config
- libtool
- expat
- autoconf
- automake
- libffi
- openssl
- python (we've already installed this in chapter 7, but we need to reinstall it, this time including pip/setuptools)
- ninja
- meson
I installed them in the order listed above.
The fourteenth package is fakeroot. Download its source tarball and the three patch files, then run these commands:
patch -p1 -i fakeroot-1.25.3-glibc-2.33-fix-1.patch
patch -p1 -i fakeroot-1.25.3-glibc-2.33-fix-2.patch
patch -p1 -i fakeroot-1.25.3-glibc-2.33-fix-3.patch
# Don't install docs
sed -i 's/SUBDIRS=doc \(.*\)/SUBDIRS=\1/' Makefile.am
./bootstrap
./configure --prefix=/usr \
--libdir=/usr/lib/libfakeroot \
--disable-static \
--with-ipc=sysv
make
make install
install -dm0755 "/etc/ld.so.conf.d/"
echo '/usr/lib/libfakeroot' > "/etc/ld.so.conf.d/fakeroot.conf"Installing pacman
Download and install pacman:
meson --prefix=/usr \
--buildtype=plain \
-Ddoc=disabled \
-Ddoxygen=disabled \
-Dscriptlet-shell=/usr/bin/bash \
-Dldconfig=/usr/bin/ldconfig \
build
meson compile -C build
meson install -C buildThis will have installed, amongst others, the makepkg.conf and pacman.conf config files in /etc; you may want to edit them. For makepkg.conf, be sure that CARCH and CHOST are appropriate, e.g.:
CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"You can set your name and email address as the PACKAGER if you want, and set MAKEFLAGS to something appropriate for your system.
It seems like pacman expects bash to be at /usr/bin/bash when launching post-install hooks. Bash is at /bin/bash in our system, so make a symlink:
ln -sv /bin/bash /usr/bin/bash
eli-schwartz
weirdbeardgame
Asome10121
Hussein-Playz
So, I don't know if you care enough to update this guide or not in any sense but I've sorta taken on this challenge with the more modern LFS build system and pacman package. The first biggest change. pacman has switched from configure / make to meson. This still works because meson has a Dest Dir option so you can set
DESDIR=$LFSto install in the temporary toolchain. Pacman has several other depends like Doxygen now that aren't listed.The biggest thing I've found in doing this with the updated pacman and LFS. You CANNOT build pacman in the LFS Chroot environment. Or at least I don't seem to be able to. While I was able to get it's depends installed like libxml2. Everytime you run the meson build script it'll reference a tool that get's installed with libxml2 that will always err out in the chroot environment even though it built and installed properly with the $LFS destdir.
It seems the best approach is to run with LFS up to the chroot ensuring you can actually enter and exit the functioning chroot but don't close or remove the original temp environment lfs user. Instead once the chroot is active and working and you've confirmed that. Use the host system's package depends to compile and install pacman with the
DESTDIR=$LFS meson install -C buildcommand from there. Then switch to the chroot environment and you'll hopefully have a working pacman you can continue with.