Skipping live ebuilds given due to land in 6.7+6.8 "soon" (in 6.9 atm),
albeit unknown if 6.7.3 and 6.8.0 branches will get it before release
and should check on bump.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
This is ancient brittle code -- an ancient, unmaintained version of GCC.
It exists solely to provide access to an ancient, unmaintained version
of libstdc++.so for ancient, unmaintained binaries that cannot be
rebuilt.
It doesn't need to be fast, or have cool CFLAGS. People shouldn't even
be using it at all. The people who do use it care about compatibility
more than anything else, so successfully compiling it should be taken as
the gift that it is.
With that in mind, we basically strip all flags. We preserve some
existing logic to handle -march= values known to exist in this old gcc,
and we continue to support -O levels, but we go no further. It's
entirely impractical to support arbitrary flags, since every gcc release
adds more flags that old versions don't support and then this fails
because GCC 3's internal xgcc build cannot handle them.
We also take this opportunity to add a workaround for modern C. New
versions of GCC barf on some of the code here because it is not legal
C99, but again, the point of this package is to provide legacy
compatibility for ancient binaries, so... we assume if it ever worked
before, it still works. :) Thus, suppress the errors. In order to
suppress the errors, we make a wrapper script around the external
compiler (not the xgcc one) so that we can apply flags that only affect
modern compilers, and aren't parsed by xgcc which would choke on them
due to those flags being too new.
Closes: https://bugs.gentoo.org/879775
Closes: https://bugs.gentoo.org/919184
Closes: https://bugs.gentoo.org/832016
Closes: https://bugs.gentoo.org/923112
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Per the comment, already couldn't use system's libvpv when USE=vaapi
is enabled (this is intentionally enforced by the build system rather
than "broken"), and now USE=-vaapi fails to build in 6.8 with system's.
Seems like an easy fix but (even if fixed) feel it would be simpler
keep the same setup regardless of USE=vaapi until vaapi allows using
system's. I hardly test USE=-vaapi and missed that it broke, and I
assume this holds for upstream too.
qtwebengine does keep bundled libvpx either up to date or backports
security fixes, albeit bumps are less frequent and fixes could lag a
bit (not that we had a choice with USE=vaapi either way, unless drop
vaapi support).
As a small perk, it'll spare users from rebuilding qtwebengine on
libvpx subslot bumps which happen now and then.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>