https://bugzilla.redhat.com/show_bug.cgi?id=2152207
--- Comment #9 from František Zatloukal <fzatlouk(a)redhat.com> ---
(In reply to Sandro Mani from comment #8)
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
Thanks, this did the trick, -debuginfo processing went fine, however, I am now
back to "Empty %files file
/builddir/build/BUILD/dxvk-2.0/debugsourcefiles.list" with -debugsource :'(
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2152207