| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
systemd-man-pages-250.tar.xz has no additional leading components.
An errata is required.
|
| | |
|
| |
|
|
|
|
|
|
| |
* update to expat-2.4.7 (#5019)
* update to bc-5.2.3 (#5020)
* update to linux-5.16.14 (#5021)
* update to perl-5.34.1 (#5022)
* update to vim-8.2.4567 (#4500)
|
| |
|
|
|
|
|
|
|
|
| |
Change pdf generation to use 9 point fonts for monospace
sections of the book. Otherwise texy overflows, especially
in Chapter 8, Stripping.
Fix a minor spacing issue in the stripping issue.
MAke a minor grammar fix in creatingfiles.xml.
|
| |
|
|
|
|
|
| |
mention nss/tst-nss-files-hosts-long failure
It seems I was confused by the two failures with similar name, when I
added the description.
|
| |
|
|
|
|
|
|
| |
This prevents a reference to /var/run in /usr/lib/tmpfiles.d/dbus.conf,
which would cause a warning from systemd-tmpfiles.
--with-system-pid-file=/run/dbus/pid is not needed with this, but
--with-console-auth-dir and --with-system-socket are still needed.
|
| |
|
|
|
| |
devtmpfs already contains many device nodes created by the kernel once
it's mounted, and Udev creates or renames nodes based on kernel work.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to match the "new" way of device handling with devtmpfs (already
widely used in recent ten years).
In a normal booting process, the kernel mounts devtmpfs at very early
stage. So the static nodes won't be used at all. The only situation
where the kernel can't mount devtmpfs is "/dev is missing", but it means
those two static nodes can't exist anyway, and a normal LFS system
(without initramfs) won't boot in such a bad situation.
Removing static /dev/console and /dev/null may cause trouble for those
people or scripts chroot into LFS tree without mounting devtmpfs. But
entering a chroot with only console and null in /dev is already
problematic. For a reference, If a systemd service is started with
PrivateDevices=true, systemd will create 18 nodes and symlinks to form a
"minimal" /dev.
|
| |\ |
|
| | | |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | | |\
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | | |
It's consistent with other commands in the same page, and also helpful
for porting to targets with different triplets (-musl or -gnuabi64).
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
It should have been removed in 10.1, and in 11.0 there should have been
"the version of LFS has switched to a merged-/usr layout". But we just
forgot to update this all the time :).
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* Update to meson-0.61.2.
* Update to linux-5.16.12.
* Update to MarkupSafe-2.1.0.
* Update to dbus-1.14.0.
* Update to vim-8.2.4489.
|
| | | |
|
| | | |
|
| |\| |
|
| | |\
| |/
|/| |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Device Drivers section in the systemd kernel configuration.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
There is also a "GCC_FOR_TARGET" which was not set correctly. The
--target=$LFS_TGT parameter can set up all of these variables as we
expected.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Now adjusting.xml only serves as a historical reference, and a "snip
library" for gcc.xml. Put all relevant content into gcc.xml directly
and remove adjusting.xml. If someone needs a historical reference, he
can always get adjusting.xml in Git history.
|
| | |
| |
| |
| |
| | |
It only adds -m64 on x86_64 GNU/Linux. In 64-bit LFS -m64 is the
default.
|
| |/
|
|
|
|
|
|
|
| |
This is the issue preventing us from cross-compiling libstdc++ in
Chapter 6. By fixing this issue we can remove a seperate pass 2 for
libstdc++ and simplify the instruction.
The upstream fix will be released in 11.3 and 12.0, so we can remove the
first sed upgrading gcc next time.
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
For systmed-250, systemd-time-wait-sync.service is disabled by
systemctl preset-all.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
on the systems without non-loopback IP address
We'd observed this long ago with "unknown reason". I just saw it again
and did some investigation, found it depends on getaddrinfo() with
AI_ADDRCONFIG, which requires a non-loopback address.
|
| |
|
|
| |
warn about the difference between release tarballs and repo snapshots
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A requirement on Glibc is not needed at all. It's enough once
$LFS_TGT-* is runnable. A test on Alpine (using musl as libc) has
practically proved this.
We'd raised binutils and GCC requirements mostly for Glibc. But now
Glibc is cross compiled by our cross toolchain with latest GCC and
binutils release, the host tools really does not matter. In the Glibc
building process only two .c files are build with BUILD_CC (the C
compiler from the host), and they are highly conservative (mostly
unchanged for years).
Binutils does not have too much requirement on host GCC & Binutils:
there is even a Binutils commit in this week fixing a build failure with
GCC-4.2!
So the most strict limitation comes from GCC. GCC requires host GCC to
support ISO C++ 11 so GCC >= 4.8 is needed. And both GCC-4.8 and latest
GCC-11.2 claims a requirement for Binutils-2.12 (for x86_64) or 2.13.1
(for 32-bit x86), so we make minimal Binutils version 2.13.1.
And, host bzip2 is never used now: the only .tar.bz2 files are elfutils
and python docs. They are not decompressed before entering chroot.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Approved by bdubbs for 11.1.
To editors: no need to rebuild system and re-tag anything, AFAIK nothing
in BLFS uses libsubid now. You may delete /usr/lib/libsubid.a on your
system manually.
|
