https://bugzilla.redhat.com/show_bug.cgi?id=2152207
--- Comment #8 from Sandro Mani manisandro@gmail.com --- The problem is that /usr/lib/rpm/mingw-find-debuginfo.sh expects any windows binaries to exist below the respective mingw prefix (say /usr/x86_64-w64-mingw32). Here however, the binaries are installed to a native prefix, say
/usr/lib64/wine/x86_64-windows/dxvk-d3d11.dll
The problem with the binaries being placed outside a mingw prefix is that mingw-find-debuginfo.sh wouldn't be able to easily figure out whether they belong to mingw32, mingw64 or ucrt64 (at least, without inspecting the binaries themselves to figure out 32 vs 64 vs ucrt).
A hacky solution here would be to manually generate the mingw64-debugfiles.list file with
%{buildroot}/usr/lib/debug/usr/lib64/wine/x86_64-windows/dxvk-d3d9.dll.debug %{buildroot}/usr/lib/debug/usr/lib64/wine/x86_64-windows/dxvk-d3d10core.dll.debug %{buildroot}/usr/lib/debug/usr/lib64/wine/x86_64-windows/dxvk-d3d11.dll.debug %{buildroot}/usr/lib/debug/usr/lib64/wine/x86_64-windows/dxvk-dxgi.dll.debug
since you can be sure that these dlls are mingw64 (resp mingw32-debugfiles.list in the 32bit case).