Bug 914040 – app-emulation/dxvk-2.3 fails to compile (PYTHON-3.12-SYSTEM)

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Agostino Sarubbo 2023-09-12 09:49:33 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: app-emulation/dxvk-2.3 fails to compile (PYTHON-3.12-SYSTEM).
Discovered on: amd64 (internal ref: python-3.12_tinderbox)

NOTE:
(PYTHON-3.12-SYSTEM) in the summary means that the bug was found on a machine that runs python-3.12 but this bug MAY or MAY NOT BE related to the new python version

[Comment 1 Agostino Sarubbo 2023-09-12 09:49:35 UTC]

Created attachment 870335 [details]
build.log

build log and emerge --info

[Comment 2 Agostino Sarubbo 2023-09-12 09:49:36 UTC]

Created attachment 870336 [details]
1-meson-log.txt

1-meson-log.txt

[Comment 3 Agostino Sarubbo 2023-09-12 09:49:36 UTC]

Error(s) that match a know pattern:


../dxvk-2.3/meson.build:1:0: ERROR: Unable to detect linker for compiler `x86_64-w64-mingw32-gcc -m32 -mfpmath=sse -Wl,--version -O2 -mtune=generic -march=x86-64 -fno-stack-protector -fno-stack-clash-protection -fno-stack-check -fcf-protection=none -U_FORTIFY_SOURCE -g3 -ggdb3 -fno-common -fno-omit-frame-pointer -fsanitize=address -mno-avx -Wl,-O1 -Wl,--as-needed -static-libasan`
stderr: x86_64-w64-mingw32-gcc: fatal error: cannot read spec file ‘libsanitizer.spec’: No such file or directory
stderr: x86_64-w64-mingw32-gcc: fatal error: cannot read spec file ‘libsanitizer.spec’: No such file or directory

[Comment 4 Agostino Sarubbo 2023-09-12 09:50:15 UTC]

asan probably should be stripped out.

[Comment 5 Ionen Wolkens 2023-09-12 10:11:16 UTC]

I don't think so, this is not something to be used globally on a whim imo, this gets used when needed. There are quite a lot of other similar flags that are going to be issues, and not going to be maintaining a list of these.

[Comment 6 Ionen Wolkens 2023-09-12 10:11:34 UTC]

*** Bug 914043 has been marked as a duplicate of this bug. ***

[Comment 7 Ionen Wolkens 2023-09-12 10:15:25 UTC]

Not to mention that these ebuilds already do strip-unsupported-flags, haven't checked why it did not get stripped, but that the flag stays may be an issue with the eclass instead.

[Comment 8 Agostino Sarubbo 2023-09-12 10:31:37 UTC]

(In reply to Ionen Wolkens from comment #5)
> I don't think so, this is not something to be used globally on a whim imo,
> this gets used when needed. There are quite a lot of other similar flags
> that are going to be issues, and not going to be maintaining a list of these.

I agree, similar bugs won't be reported anymore