Per Robert on the bug:
> libksysguard 6.3.0 fails to build when using the LLVM profile because it now uses
> std::jthread and std::stop_token that llvm's libc++ considers experimental
> and does not build by default.
They're unleashed in libcxx 20 which should be released shortly. In the meantime,
pass -fexperimental-library.
Closes: https://bugs.gentoo.org/949636
Thanks-to: Steffen Hau <steffen@hauihau.de>
Thanks-to: Robert Holt <holt.r94@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
We've been waiting for this (alpha) release for a while (7 years!):
https://lists.gnu.org/archive/html/bug-patch/2024-05/msg00000.html
It is now here and all remaining issues appear to have been resolved, so
this is most likely going to be effectively what the final release looks
like too. Based on discussion, it appears to be the correct move to
keyword this now, moving on from the situation of having many patches
and fixing some Modern C issues etc.
Acked-by: Sam James <sam@gentoo.org>
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Real "wine64" only existed with USE="abi_x86_64 -wow64" but this
now has a new loader only installed as "wine" regardless of USE.
Many scripts still try to call wine64 though, will likely keep
the symlink for a while.
wine-preloader and wine64-preloader are also both gone, but not
aware of anything using these.
wrt the man pages bit for that block, seem they get installed
properly even if USE"abi_x86_64 -abi_x86_32" now likely thanks
to the same change.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Formerly this was a mean to ensure REPLACING_VERSIONS had only
one element for ver_test, but this is not using ver_test anymore.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Some kernel config options are renamed and to allow users to run
libvirt on older kernels we had to check kernel version and
either include old or new name in CONFIG_CHECK.
Well, I think it is safe to assume nobody runs the most recent
libvirt on 4.X or <5.2 kernels and thus these workarounds can be
dropped.
Just to be on the safe side, let's make the change only for the
live ebuild for now.
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/40566
Signed-off-by: Sam James <sam@gentoo.org>
Mask message tries to clear up user confusion, has a history
of users keeping it in @world or requesting version bumps while
unaware that the package is not being used by >=wine-8
Also, while we were still bumping & stabilizing this, we were not
really testing it with wine-7 and unclear if new versions even
still worked with it.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Technically needs a revbump, but this only affects the semi-unsupported
USE=crossdev-mingw with ~arch toolchain given mingw64-toolchain is not
using binutils-2.44 yet (no plans for a while in case of more issues).
Little sense in having typical users rebuild all installed wine(s) esp.
given haven't even gotten a downstream bug report yet beyond a mention
on IRC.
If you are affected (wine will be entirely broken, even winecfg won't
start), then please re-emerge wine & update prefixes. May optionally
want to consider switching to mingw64-toolchain if want to stick to a
tested-with-wine toolchain while at it.
Patch seems to work fine as-is for old versions beside offsets.
For proton it is unclear if it will be still needed when Valve switches
to 10.x given they will likely base it on stable 10.0 rather than
>=10.2, albeit a fixed 10.0.1 might exists before then. Keeping it in
live ebuild for now.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Haven't tried this old version but, like the others, this is likely
broken with mingw binutils-2.44 and backporting the fix for that only
applies to >=wine-8 as-is. Seems time to drop support for this one.
There is no indication that Valve will ever release a (fixed) new
version of this branch.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Haven't tried this old version but, like the others, this is likely
broken with mingw binutils-2.44 and backporting the fix for that only
applies to >=wine-8 as-is. Seems time to drop support for this one.
Even if upstream ever releases a (fixed) 7.0.3, this version also
needed extra attention due to being before several PE migrations
and blocks last-riting non-PE vkd3d that would rather not maintain
only for wine-7. So keeping it is unwanted.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>