| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
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.
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
bootctl is not built because LFS doesn't have gnu-efi.
systemd-cryptenroll is disabled if cryptsetup is not installed (should
be added into BLFS).
|
|
|
|
|
| |
Add lto-dump and libitm, and reword description for liblto_plugin
because it's actually used by libbfd (from binutils).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Add libc_malloc_check.so (it's like libmcheck.a, but should be used with
LD_PRELOAD).
Add description for libmvec.
"libnss" -> "libnss_*", and reword the description.
|
|
|
|
|
| |
This fix was found on an i368 system when building openjdk. The
fix does not help or hurt x86_64 systems.
|
|
|
|
|
| |
Prevent from misleading people to think "I don't build binutils with LTO,
so I can skip the patch".
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
I just received a private mail from some guy obviously puzzled by this
switch. Expand the explanation a little to make it more clear.
|
|/
|
|
|
|
|
|
|
| |
Add binutils-2.38 LTO patch.
Update to util-linux-2.37.4.
Update to man-db-2.10.1.
Update to linux-5.16.9.
Update to vim-8.2.4383.
Update to iana-etc-20220207.
|
|
|
|
|
|
|
| |
Quote from the NEWS file:
A symbolic link to the dynamic linker is now installed under
/usr/bin/ld.so (or more precisely, '${bindir}/ld.so').
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A very old libtool copy (2009-11-29) is shipped in binutils tarball. It
does not support sysroot, so the cross-built binutils binaries may link
to libraries from the host distro, if certain libraries are available.
The ideal solution should be updating libtool, as libtool-2.4.6 (in LFS)
has sysroot support. However, updating libtool for binutils is not
trivial: it would require to rerun autoconf and binutils building system
sticks to autoconf-2.69. Another issue is the sysroot support for
libtool has introduced a configure option "--with-sysroot", which
conflicts with an already existing option with the same name in
GCC and binutils building system (we are using the GCC/binutils version
of --with-sysroot in chapter 5).
GCC building system has --with-build-sysroot (we are using this for GCC
pass 2) for this issue. Binutils copied GCC building system, but it
does not respect --with-build-sysroot.
So for now we just edit libtool code to prevent "-L/usr/lib" in
$LFS_TGT_gcc command line. It should fix the issue about host libiberty
(reported in #lfs-support) as well, but it still need to be confirmed by
someone having such a host.
Tested with a jhalfs run on LFS.
|
| |
|
|
|
|
|
|
| |
Update to bc-5.2.2.
Update to linux-5.16.8.
Update to binutils-2.38. Requires adding zlib to Chapter 6.
|