This is a dead project, but the comment in the code claims the
cdio_realpath function is designed to emulate POSIX realpath while the
test case is not using POSIX-compatible realpath correctly. So it seems
a test case issue, only document it instead of fix.
Note that this test has started to fail since Glibc-2.36, not 2.37. But
somehow we didn't catch it before.
This package does not use libmpeg2. The mpeg2 encoder depends on some
packages not in BLFS. The mpeg2 decoder has been moved to ugly.
One test is skipped w/o libsoup2. Two tests related to rtp fails w/o
gst-plugins-good.
The first AVX2-capable CPUs are released in 2013 (ten years ago)
and now all recent Intel Core and AMD Ryzen models support it. So
it makes sense to enable it now. AVX512F is much uncommon now for
non-server CPU models (only Rocket Lake, Alder Lake with E-cores
disabled, and Zen 4), so leave it as <option>.
In the changelog of flac-1.4.2:
* Remove xmms plugin (Martijn van Beurden, TokyoBlackHole)
* Remove all pure assembler, removing build dependency on nasm
Adjust the description of man page Xserver.1: technically both Xorg and
Xwayland are in the category of "X server". The reason we don't install
it here is not "it's not a part of this package", but we don't want to
overwrite a man page from another package.
Remove the creation of /etc/X11/xorg.conf.d: "Xorg" is "another X
server" so technically Xwayland (and other packages except Xorg and the
Xorg drivers) should have nothing to do with it. In my last build
/etc/X11/xorg.conf.d is empty.
I tried it and it refuse to build with --disable-static. When I removed
--disable-static, I still got about 500 test failures with
--enable-python, but without it the test runs normally.
Though the option is still named gtk_doc, actually it invokes gi-docgen.
By the way, run the tests with dbus-run-session or almost all will fail
w/o a d-bus address.
And remove the test failure caused by a previous installed version: the
upstream claims it's already fixed (the same story as gnutls and
-disable-rpath workaround).
The most likely reason to rerun a scripted build of rust is that
something failed during build. But since this directory is created at
the beginning of the script, the script will fail early cresting the
directory.
Of course, now, there is no protection against erasing a successful
build when rerunning with different options.
