diff options
| author | Ionen Wolkens <ionen@gentoo.org> | 2024-03-24 14:26:51 -0400 |
|---|---|---|
| committer | Ionen Wolkens <ionen@gentoo.org> | 2024-03-24 14:37:35 -0400 |
| commit | f96312e128119688fc59d2f8b34f362c4546ff3d (patch) | |
| tree | 46f3e8131b84de24236f6a6cd04fdc8cfcea43db /dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-1.4.0.ebuild | |
| parent | 6da4ec59b0cea1506aebfdde8d5d526a78a792b9 (diff) | |
| download | gentoo-f96312e128119688fc59d2f8b34f362c4546ff3d.tar.gz gentoo-f96312e128119688fc59d2f8b34f362c4546ff3d.tar.bz2 gentoo-f96312e128119688fc59d2f8b34f362c4546ff3d.zip | |
app-emulation/wine-vanilla: 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/libjson-rpc-cpp/libjson-rpc-cpp-1.4.0.ebuild')
0 files changed, 0 insertions, 0 deletions
