| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
You can't throw a NVIDIA GTX 690 into /dev.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Well, somehow this paragraph has become too imprecise.
1. We don't support IA64. Both Intel and AMD uses x86_64 now, which is
referred as "AMD64" because it's first proposed by AMD. Intel
attempted to use IA64 (which is a VLIW architecture completely
different with x86_64) to compete with AMD64, but failed. Then Intel
adapted x86_64.
2. The architecture specific part belongs to Core and Desktop.
3. LFS cannot conform to both AMD64 and IA32 because we don't support
multilib. It's "or", not "and".
|
|
|
|
| |
of the simple present to make the order of events clearer.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to introduce some variety by rephrasing "This package contains ...".
|
| |
|
| |
|
|
|
|
| |
punctuation here and there.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to iana-etc-20221007.
Update to vim-9.0.0739.
Add upstream patches to readline and bash.
Update to zlib-1.2.13.
Update to man-pages-6.00.
Update to gettext-0.21.1.
Update to iproute2-6.0.0.
Update to meson-0.63.3.
Update to Python-3.10.8.
Update to xz-5.2.7.
Update to tzdata-2022e.
Update to linux-6.0.1.
Update to dbus-1.14.4.
|
|
|
|
|
| |
Some kernel features (like, building the kernel with LTO) already
requires Clang.
|
| |
|
| |
|
|
|
|
|
| |
In bash-5.2 tarball config.guess is not executable, so we need to run
the script with an explicit "sh".
|
| |
|
|
|
|
|
|
| |
When I changed the sanity check to remove the "dummy.c" file, I
inadvertently used "gcc" instead of "$LFS_TGT-gcc". Which of course
finds the host gcc...
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Update to Linux-5.19.13
If you are using a laptop with an Intel GPU, it's imperative that you
update immediately if you are running Linux-5.19.12. Failure to upgrade
may result in permanent damage to the LCD display on your laptop.
The root cause of this is improper backporting of bugfixes for the i915
DRM driver in the kernel.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I have:
2 FAIL
5092 PASS
67 UNSUPPORTED
16 XFAIL
4 XPASS
Let's not be too precise (or we'll need to explain the meaning of
"UNSUPPORTED"). IMO "over 5000" is fine (until we get 5500 tests).
|
|
|
|
|
| |
"gold" is not an installed program (it's named "ld.gold"). So IMO it's
not proper to use <command>.
|
|
|
|
| |
Again, I sincerely wish libtool can suffer a painful death.
|
| |
|
|
|
|
|
|
|
|
| |
to root
Many users will create a user with the same username and UID so the
files will still be owned by his/her. So make it optional by "If you
won't assign the same UID for your user in the LFS system".
|
|
|
|
| |
/dev/shm may be a mount point, or a symlink.
|
|
|
|
|
| |
Now that /dev/shm is always a mountpoint, it needs to be umounted
otherwise dev cannot be umounted.
|
| |
|
| |
|
|
|
|
| |
You cannot throw a NVIDIA GTX 690 into /dev :).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you are using a "modern" distro (with devtmpfs and a modern udev
implementation), a bind mounting is actually not needed because you can
mount devtmpfs anyway. The only reason for bind mounting is to be
compatible with old host distros where /dev is a directory containing
many static device nodes, or is a tmpfs (not same as devtmpfs) popluated
by bootscript or an old udev (modern udev implementations, including
eudev and systemd-udev used by LFS, strictly requires a devtmpfs on
/dev).
So update the explanation to match the status quo.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chroot command itself does not require kernel VFS mounted. You can mount
/proc, /sys, and /run after entering chroot with
"mount -v -t proc proc /proc" etc. For /dev, if the host kernel
supports devtmpfs, you can also mount /dev in chroot with
"mount -v -t devtmpfs devtmpfs /dev". Even if the host does not support
devtmpfs, it's still possible to mount /proc in chroot, then use
"mount --bind /proc/1/dev /dev".
It's just LFS editors decide to mount them before chroot. So reword
some untrue assertions.
|
| |
|
|
|
|
|
| |
Added clarification; the virtual file systems expose certain information
to programs in user space; chroot won't work without them.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I'm pretty sure "stage 2" libstdc++ (installed in ch6) is already fully
featured. The reason to rebuild the stage 3 libstdc++ (or entire
stage 3 gcc) is same as the reason to rebuild every packages in multiple
chapters: to "settle down" it.
Merge the content of
https://www.linuxfromscratch.org/lfs/faq.html#rebuild-ch8 into the book
as an explanation.
|
| |
| |
| |
| | |
field
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Don't say "most building system", refine the dicussion for autoconf.
Other building systems may use a variant of triplet, or use a
completely different system designation.
- Explain why a triplet may contain 4 fields in detail. "Histroical
reason" is not really correct because 3-field triplet is still used
today for BSD, Fuchsia, IOS, Mac OS X (darwin), Solaris, etc.
- "machine" triplet to "system" triplet (strictly speaking, only the
first field in the triplet is for the machine).
Why we need to say "vendor can be omitted" explicitly: we mention "gcc
-dumpmachine". On some distros (like Ubuntu) the output has no vendor
field. If you think this is too nasty, please remove both.
|
| |
| |
| |
| |
| |
| | |
Update to bc-6.0.4.
Update to linux-5.19.12.
Fix an xml error.
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Update to iana-etc-20220922.
Update to tzdata-2022d.
Update to readline-8.2.
Update to linux-5.19.11.
Update to libffi-3.4.3.
Update to libcap-2.66.
Update to dbus-1.14.2.
Update to bc-6.0.3.
Update to bash-5.2.
|
| |
|
|
|
|
|
|
| |
This reverts commit 0665add6d87f16f772c131e197ebb7c8bc67df50.
new version of bash is not yet in the book!
|
| |
|
| |
|
|
|
|
|
| |
Since r11.0-r199, libstdc++ pass 2 is built as a part of gcc pass 2, not
in chroot.
|
|
|
|
| |
"Pass 1" and "Pass 2" have specific meaning in LFS.
|
|
|
|
|
|
|
|
| |
"need to be cross compiled" alone does not make too much sense: we
compile these packages in chapter 8 anyway. The real reason forcing a
cross compilation is circular dependency: if building A needs B but
building B needs A, we'll have to cross compile at least one of A and B
or we won't be able to build either in the chroot.
|