summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIonen Wolkens <ionen@gentoo.org>2024-03-28 06:05:56 -0400
committerIonen Wolkens <ionen@gentoo.org>2024-03-28 06:10:06 -0400
commit18bba14d15e78f2572f74788d2557e095b91ddfb (patch)
tree58e03a04f1394d9eadd393322d4085e79eba849b /dev-python/pybind11
parentapp-emulation/vkd3d-proton: filter -Wl,-z,* ... for C(XX)FLAGS (diff)
downloadgentoo-18bba14d15e78f2572f74788d2557e095b91ddfb.tar.gz
gentoo-18bba14d15e78f2572f74788d2557e095b91ddfb.tar.bz2
gentoo-18bba14d15e78f2572f74788d2557e095b91ddfb.zip
app-emulation/dxvk: filter -Wl,-z,* ... for C(XX)FLAGS
strip-unsupported-flags handles this fine in LDFLAGS, but -Wl,* are no-ops during compile-only tests (thus not stripped) and then if a package compiles and links anything at same time it fails. This used not to be a big problem but now that 23.0 profiles do -Wl,-z,pack-relative-relocs (mingw ld has no -z) this is hitting bashrc-mv users that tend to do CFLAGS="${LDFLAGS}" by default. Tempting to ignore it because of how wrong it is, but well. An alternate route could be to eventually have strip-flags and/or strip-unsupported-flags remove -Wl,* from non-LDFLAGS given this could affect more than mingw (e.g. switching to bfd when there is a lld-only option). wrt bug #928038, this already been done a while ago for wine, mingw64-runtime, and mingw64-toolchain itself and there *should* have been only dxvk and vkd3d-proton left (now done). Closes: https://bugs.gentoo.org/928038 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-python/pybind11')
0 files changed, 0 insertions, 0 deletions