aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove all non header files in linux headers11.2Pierre Labastie2022-08-311-2/+1
| | | | | Report by Joe Locash that a perl script was left in /usr/include with our current instructions
* lfs-11.2Bruce Dubbs2022-08-313-8/+16
|
* parition: mention EFI system partitionr11.2Xi Ruoyao2022-08-281-0/+5
| | | | Text only change. Simply refer to BLFS.
* python: supress "failed to check new pip version" or "a new pip version is ↵Xi Ruoyao2022-08-261-2/+14
| | | | | | available" warnings The non-text change during freeze is approved by bdubbs.
* grub: add a note about filesystem UUID and partition UUID usageXi Ruoyao2022-08-261-0/+32
| | | | Text only change.
* reboot: mention firmwaresXi Ruoyao2022-08-261-0/+5
| | | | | | Text only change. I've forgotten this several times for AMDGPU...
* grub: update description for grub-glue-efiXi Ruoyao2022-08-261-2/+1
| | | | | | | Text only change. Found out this utility also exists on ARM, so copied "grub-glue-efi --help" here, which does not mention "ia32" or "amd64".
* Don't use dummy.c for glibc sanity check in chap 5Pierre Labastie2022-08-251-5/+4
| | | | | | | | It seems glibc creates dummy.c for its own use. This leaves some dummy.xxx files in the directory, that may lead some users to think that the directory is not properly cleaned up after the test (I did :) So use a pipe so that only a.out is created
* linux kernel: reword description for CONFIG_X86_X2APICXi Ruoyao2022-08-251-4/+6
|
* glibc: don't mention "/lib" as ld.so search path anymoreXi Ruoyao2022-08-241-4/+3
| | | | | | | | | Text change only. Since 11.0, /lib is a symlink to usr/lib. With libc_cv_slibdir=/usr/lib, /lib won't be searched by default anymore (if someone mess up the system by removing /lib symlink and create an real directory there, for example the initramfs before r10.1-439).
* linux kernel: disable CONFIG_USERFAULTFD to avoid CVE-2022-2590 for nowXi Ruoyao2022-08-241-0/+12
|
* linux kernel: enable CONFIG_X86_X2APICXi Ruoyao2022-08-241-0/+25
| | | | | | | | | | | It's recommended for CVE-2022-21233 mitigation. And, if the BIOS has enabled x2APIC but CONFIG_X86_X2APIC=n, the kernel will panic on boot. If x2APIC is disabled or not available, the kernel with CONFIG_X86_X2APIC=y can still boot normally. No need to tag anything again because interrupt handling cannot affect userspace.
* glibc: update test statusXi Ruoyao2022-08-231-10/+6
| | | | | | | Text change only. Add tst-arc4random-thread failure recently reported to upstream, remove namespace related failures as they are UNSUPPORTED now in 2.36.
* mark linux-5.19.2 and shadow-4.12.2 as security fixXi Ruoyao2022-08-221-2/+2
|
* Update SBU times and disk usage for all packagesBruce Dubbs2022-08-211-96/+91
|
* Minor updatesBruce Dubbs2022-08-213-17/+17
|
* Update stats for systemd packages in preparation of 11.2-rc1Douglas R. Reno2022-08-211-6/+6
|
* stripping: also mention symbol table bisides debug symbolsXi Ruoyao2022-08-211-3/+9
|
* shadow: fix download URLXi Ruoyao2022-08-211-1/+1
|
* add changelog entries for last package updateXi Ruoyao2022-08-211-0/+38
|
* Intermediate update prior to lfs-11.2-rc1Bruce Dubbs2022-08-207-41/+47
|
* Remove libtool archive (.la) files in Chapter 5 and 6Xi Ruoyao2022-08-195-0/+30
| | | | | | | | | | | | | | They are really harmful. In Binutils pass 2, libstdc++.la caused the building system to use host /usr/lib/libstdc++.so for gprofng. We now has disabled gprofng for pass 2, but the similar issue also exists in GCC pass 2. In a normal LFS build, the building system silently uses /usr/lib/libstdc++.so (I guess it does not blow up simply because some blind luck); in a real cross build (x86 -> ARM for example) the build will fail. Remove the .la files to fix this issue. Instead of only modifying clfs-ng, it makes more sense to apply the change for trunk: though the build does not fail, using host library is still a contamination.
* Clean chapter 8 binutils xml and textPierre Labastie2022-08-141-20/+5
| | | | | | Remove old commented instructions Remove a sed and a test failure explanation: both have been fixed in binutils-2.39
* Typo fix in changelogDouglas R. Reno2022-08-111-1/+1
|
* Package updates.Bruce Dubbs2022-08-112-19/+49
| | | | | | | | | Update to vim-9.0.0192. Update to iana-etc-20220803. Update to tzdata-2022b. Update to iproute2-5.19.0. Update to linux-5.19.1. Update to bc-6.0.1.
* typography: add a note about "Il1" or "O0" issueXi Ruoyao2022-08-111-0/+6
|
* Merge branch 'trunk' of git.linuxfromscratch.org:lfs into trunkBruce Dubbs2022-08-091-1/+11
|\
| * binutils: add desc for gprofngXi Ruoyao2022-08-091-1/+11
| |
* | Tweak pip3 instructionsBruce Dubbs2022-08-094-6/+15
|/
* Merge branch 'trunk' of git.linuxfromscratch.org:lfs into trunkBruce Dubbs2022-08-071-4/+0
|\
| * perl: remove outdated note regarding zlib versionXi Ruoyao2022-08-071-4/+0
| | | | | | | | Now perl-5.36 ships zlib-1.2.12, which is same as the book providing.
* | TypoBruce Dubbs2022-08-071-1/+1
|/
* Merge branch 'trunk' of git.linuxfromscratch.org:lfs into trunkBruce Dubbs2022-08-061-1/+1
|\
| * Update boostcript version to 2022072311.1-finalThomas Trepl (Moody)2022-08-071-1/+1
| |
* | Package updates.Bruce Dubbs2022-08-0611-32/+89
|/ | | | | | | Update to binutils-2.38. Update to util-linux-2.38.1. Update to Python3-3.10.6. Update to glibc-2.36.
* Note that linux-5.18.14 has fixes for RETBleed.Ken Moffat2022-07-241-1/+2
| | | | Security Advisory to follow.
* Package updates.Bruce Dubbs2022-07-242-6/+20
| | | | | Update to linux-5.18.14. Update to libcap-2.65.
* Mark raid array as clean at shutdownThomas Trepl (Moody)2022-07-232-0/+10
|
* another "obsoleted" -> "obsolete" fixXi Ruoyao2022-07-161-1/+1
|
* Fix kernel statsBruce Dubbs2022-07-161-3/+3
|
* Package updates.Bruce Dubbs2022-07-164-22/+48
| | | | | | | | Update to meson-0.63.0. Update to kmod-30. Update to inetutils-2.3. Update to linux-5.18.9. Update to OpenSSL-3.0.5.
* SpellingBruce Dubbs2022-07-142-2/+2
|
* python: mention that --force-reinstall needs --no-depsXi Ruoyao2022-07-021-2/+3
|
* texinfo: remove unneeded sedXi Ruoyao2022-07-022-10/+0
| | | | | | | | | | | | | | | | | | | | It works out of box with glibc-2.35. I think this issue is already fixed at glibc side, by the commit: commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82 Author: Paul Eggert <eggert@cs.ucla.edu> Date: Tue Sep 21 07:47:45 2021 -0700 regex: copy back from Gnulib Copy regex-related files back from Gnulib, to fix a problem with static checking of regex calls noted by Martin Sebor. This merges the following changes: * New macro __attribute_nonnull__ in misc/sys/cdefs.h, for use later when copying other files back from Gnulib. ... ... (unrelated things trimmed)
* Fix vim doc directoryBruce Dubbs2022-06-301-1/+1
|
* Package updates.Bruce Dubbs2022-06-303-21/+57
| | | | | | | | | | Update to vim-9.0.0006. Update to iana-etc-20220610. Update to OpenSSL-3.0.4. Update to kbd-2.5.1. Update to linux-5.18.8. Update to bc-5.3.3. +
* Generate shared C++ bindings for ncursesPierre Labastie2022-06-293-24/+82
| | | | | | | | Presently we let the build system generate static C++ bindings, and then we remove them. Note that we could also prevent generating any C++ binding, since nothing in LFS/BLFS use them, but it seems to me that generating the shared ones is closer to what is done for other packages.
* bootscripts: change obsoleted egrep to grep -EXi Ruoyao2022-06-232-2/+2
|
* grep: mark egrep and fgrep obsoleteXi Ruoyao2022-06-231-2/+4
| | | | | | | They are deprecated since 2007, and the next grep release (3.8 or 4.0) will print a warning if they are used. Url: https://git.savannah.gnu.org/cgit/grep.git/commit/?id=a951562
* openssl: mark c_rehash obsoleteXi Ruoyao2022-06-231-2/+5
| | | | | | | | | | | | | | The c_rehash script, shipped by OpenSSL versions in current LFS trunk and all previous LFS releases, is vulnerable to CVE-2022-2068. It's fixed in 3.0.4, but OpenSSL 3.0.4 is completely broken on CPU models with AVX-512 extension [1]. So we'd like to defer OpenSSL update and wait for upstream consensus about "would 3.0.5 be released in urgency". But, the upstream has announced that use of c_rehash is obsolete now [2]. So we can tell people not to use it. [1]: https://github.com/openssl/openssl/issues/18625 [2]: https://www.openssl.org/news/secadv/20220621.txt
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-20 09:40:43 +0000