summaryrefslogtreecommitdiff
path: root/dev-cpp/jwt-cpp/jwt-cpp-0.6.0.ebuild
diff options
context:
space:
mode:
authorIonen Wolkens <ionen@gentoo.org>2024-03-24 14:30:37 -0400
committerIonen Wolkens <ionen@gentoo.org>2024-03-24 14:37:35 -0400
commit5d08c93d5ec41658468afe23cc0cb816ad682fd1 (patch)
treed7ea0b7fb0e3cf824287609b4faf5cf890ed8635 /dev-cpp/jwt-cpp/jwt-cpp-0.6.0.ebuild
parentf96312e128119688fc59d2f8b34f362c4546ff3d (diff)
downloadgentoo-5d08c93d5ec41658468afe23cc0cb816ad682fd1.tar.gz
gentoo-5d08c93d5ec41658468afe23cc0cb816ad682fd1.tar.bz2
gentoo-5d08c93d5ec41658468afe23cc0cb816ad682fd1.zip
app-emulation/wine-staging: filter -Wl,-z,* ... for CFLAGS
test-flags-CC was not meant to test LDFLAGS and -Wl,* are no-ops at compile-time and thus don't get stripped even if they don't work (same happens when using strip-unsupported-flags) 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). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-cpp/jwt-cpp/jwt-cpp-0.6.0.ebuild')
0 files changed, 0 insertions, 0 deletions