summaryrefslogtreecommitdiff
path: root/dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-1.4.0.ebuild
diff options
context:
space:
mode:
authorIonen Wolkens <ionen@gentoo.org>2024-03-24 13:13:04 -0400
committerIonen Wolkens <ionen@gentoo.org>2024-03-24 14:37:34 -0400
commitf4f5384a31752bfbaf021725ac539d1522656423 (patch)
tree634664dbc5d2ab7538389744d8fbbe60be6ff092 /dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-1.4.0.ebuild
parentd2c7ce699ffbf9c9ba54b51acad2f08182dc54d9 (diff)
downloadgentoo-f4f5384a31752bfbaf021725ac539d1522656423.tar.gz
gentoo-f4f5384a31752bfbaf021725ac539d1522656423.tar.bz2
gentoo-f4f5384a31752bfbaf021725ac539d1522656423.zip
dev-util/mingw64-toolchain: filter -Wl,-z,* ... for CFLAGS
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). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-1.4.0.ebuild')
0 files changed, 0 insertions, 0 deletions