Like rustc. Move the unset command out of the <screen> for
installation because if we use sudo --preserve-env=PATH_PY311 -s for a
shell as root to install the package, "unset PATH_PY311" will only
unset it in this shell, not the shell building the package.
Also fix a grammar issue in rustc, and unset LIBSSH2_SYS_USE_PKG_CONFIG
after installing rustc too.
The mach of seamonkey is more nasty than FF or TB :(.
Q: Why not just export PATH=/opt/python3.11/bin:$PATH?
A: This will be too easy forgetting to unset it. And an explicit
PATH=$PATH_PY311 also helps sudo (sudo PATH=$PATH_PY311 mach install
will work perfectly fine, but export PATH=$PATH_PY311; sudo ... won't
work as sudo will reset $PATH).
Note that if you build something relying on $SHELL, it may still fail to
build in chroot.
In the chroot we first use "env -i" to clean the environment variables.
When bash starts with no $SHELL set, it *sets* SHELL=(the login shell
of current user specified in /etc/passwd), but it *does not export this
variable*.
For example:
$ cat > t.c << EOF
#include <stdio.h>
#include <stdlib.h>
int main() { puts (getenv ("SHELL") ?: "(nullptr)"); }
$ ./a.out
/bin/zsh/
$ cc t.c
$ env -i bash -c "echo $SHELL"
/bin/zsh
$ env -i bash -c "./a.out"
(nullptr)
We can remove this now only because Mozilla has added a workaround into
their building system at
https://hg.mozilla.org/mozilla-central/rev/5afe7b911f61 for some Mac
builder, inadvertently fixing our issue.
Link: https://lists.linuxfromscratch.org/sympa/arc/blfs-support/2014-11/msg00050.html
Link: https://lists.linuxfromscratch.org/sympa/arc/blfs-dev/2023-11/msg00136.html
If a newline is inside the comment, it won't be rendered. So we can
avoid an excessive amount of empty lines in seamonkey, and break the
long comments about RELR into multiple lines.
- Remove --enable-optimize=-O2 as it's the default.
- Use RELR for saving several MB from libxul.so, like Firefox.
- Update the comment for --disable-rust-simd.
- Copy a comment with legal implication from Firefox.
"export CC=clang CXX=clang++" is bad because it contaminates the
environment, thus if some packages are built after seamonkey in the same
shell and the user wouldn't have unset CC and CXX, those package may be
built with an untested configuration.
Move them into mozconfig. A test build has shown they still works
there.
Now all sourceforge.net subdomains have a valid SSL certificate. The
changes are automatically done via a sed. I've reviewed the changes and
reverted the changes in archive/*, pst/xml/docbook-xsl.xml, and
stylesheets/lfs-xsl/lfs-l10n.xml. Other changes should (hopefully) be
fine.
We used to sed the double_t definition to allow building, but now
we use clang, so that the build passes without sed. Say that using
GCC breaks the build in command explanations too.
Update to node.js-16.16.0
Update to php-8.1.8
Add security patch for Dovecot (fixes CVE-2022-30550)
Update to seamonkey-2.53.13
Update to gnupg-2.3.7
Mark git as a security update
