diff options
| author |   Ionen Wolkens <ionen@gentoo.org> | 2024-03-24 14:11:01 -0400 |
|---|---|---|
| committer | Ionen Wolkens <ionen@gentoo.org> | 2024-03-24 14:37:34 -0400 |
| commit | ff15377c5a378209436cbf2961ce76ba6526f070 (patch) | |
| tree | 2dac88b29e5251a64941d754bf9398b7a2f6015d | |
| parent | dev-util/mingw64-toolchain: filter -Wl,-z,* ... for CFLAGS (diff) | |
| download | gentoo-ff15377c5a378209436cbf2961ce76ba6526f070.tar.gz gentoo-ff15377c5a378209436cbf2961ce76ba6526f070.tar.bz2 gentoo-ff15377c5a378209436cbf2961ce76ba6526f070.zip | |
dev-util/mingw64-runtime: 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>
| -rw-r--r-- | dev-util/mingw64-runtime/mingw64-runtime-11.0.0.ebuild | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/dev-util/mingw64-runtime/mingw64-runtime-11.0.0.ebuild b/dev-util/mingw64-runtime/mingw64-runtime-11.0.0.ebuild index e6c64a8633a0..2fc28bcf8673 100644 --- a/dev-util/mingw64-runtime/mingw64-runtime-11.0.0.ebuild +++ b/dev-util/mingw64-runtime/mingw64-runtime-11.0.0.ebuild @@ -60,6 +60,11 @@ src_configure() { fi local CHOST=${CTARGET} + # some bashrc-mv users tend to do CFLAGS="${LDFLAGS}" and then + # strip-unsupported-flags miss these during compile-only tests + # (primarily done for 23.0 profiles' -z, not full coverage) + filter-flags '-Wl,-z,*' + # -mavx with mingw-gcc has a history of obscure issues and # disabling is seen as safer, e.g. `WINEARCH=win32 winecfg` # crashes with -march=skylake >=wine-8.10, similar issues with |