930988 – app-emulation/dxvk: ERROR: Unable to detect linker for compiler x86_64-w64-mingw32-gcc

Bug 930988 - app-emulation/dxvk: ERROR: Unable to detect linker for compiler x86_64-w64-mingw32-gcc

Summary: app-emulation/dxvk: ERROR: Unable to detect linker for compiler x86_64-w64-mi...

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	AMD64 Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2024-04-30 19:51 UTC by Samson
Modified:	2024-04-30 20:00 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
build.log (build.log,4.98 KB, text/x-log) 2024-04-30 19:51 UTC, Samson	Details
emerge --info '=app-emulation/dxvk-2.3.1-r1::gentoo' (file_930988.txt,7.20 KB, text/plain) 2024-04-30 19:52 UTC, Samson	Details
emerge -pqv '=app-emulation/dxvk-2.3.1-r1::gentoo' (file_930988.txt,113 bytes, text/plain) 2024-04-30 19:53 UTC, Samson	Details
emerge --info (file_930988.txt,7.10 KB, text/plain) 2024-04-30 19:54 UTC, Samson	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Samson 2024-04-30 19:51:05 UTC

Created attachment 892027 [details]
build.log

Can't build dxvk with mingw64-toolchain

Comment 1 Ionen Wolkens gentoo-dev

2024-04-30 19:52:01 UTC

emerge --info?

Comment 2 Samson 2024-04-30 19:52:36 UTC

Created attachment 892028 [details]
emerge --info '=app-emulation/dxvk-2.3.1-r1::gentoo'

Comment 3 Samson 2024-04-30 19:53:41 UTC

Created attachment 892029 [details]
emerge -pqv '=app-emulation/dxvk-2.3.1-r1::gentoo'

Comment 4 Samson 2024-04-30 19:54:32 UTC

Created attachment 892030 [details]
emerge --info

Comment 5 Ionen Wolkens gentoo-dev

2024-04-30 19:54:59 UTC

(In reply to Samson from comment #2)
> Created attachment 892028 [details]
> emerge --info '=app-emulation/dxvk-2.3.1-r1::gentoo'
Was wondering where that -fopenmp was coming from, and well it's in your CXXFLAGS. Generally I'd advise against doing that globally.

Surprised this didn't get stripped by strip-unsupported-flags though.

Comment 6 Ionen Wolkens gentoo-dev

2024-04-30 19:56:05 UTC

(In reply to Ionen Wolkens from comment #5)
> (In reply to Samson from comment #2)
> > Created attachment 892028 [details]
> > emerge --info '=app-emulation/dxvk-2.3.1-r1::gentoo'
> Was wondering where that -fopenmp was coming from, and well it's in your
> CXXFLAGS. Generally I'd advise against doing that globally.
> 
> Surprised this didn't get stripped by strip-unsupported-flags though.

(odds are having this will also break vkd3d-proton, maybe wine, etc...)

Comment 7 Ionen Wolkens gentoo-dev

2024-04-30 19:59:08 UTC

Similar bugs were closed as invalid for users doing global -fopenmp, e.g. bug #532020 comment #4

Guess I'll do the same, please remove it.

Comment 8 Samson 2024-04-30 20:00:24 UTC

(In reply to Ionen Wolkens from comment #6)
> (In reply to Ionen Wolkens from comment #5)
> > (In reply to Samson from comment #2)
> > > Created attachment 892028 [details]
> > > emerge --info '=app-emulation/dxvk-2.3.1-r1::gentoo'
> > Was wondering where that -fopenmp was coming from, and well it's in your
> > CXXFLAGS. Generally I'd advise against doing that globally.
> > 
> > Surprised this didn't get stripped by strip-unsupported-flags though.
> 
> (odds are having this will also break vkd3d-proton, maybe wine, etc...)

Yea without openmp dxvk start building. Other packages often give more clear errors so i use compiler-clnang-nonopenmp enviroment for them. But this error confused me.