[Bug 51694] New: Wine v6.16 build fails when both gcc and clang are available on the build system
https://bugs.winehq.org/show_bug.cgi?id=51694 Bug ID: 51694 Summary: Wine v6.16 build fails when both gcc and clang are available on the build system Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: reserv0(a)yahoo.com Distribution: --- Created attachment 70565 --> https://bugs.winehq.org/attachment.cgi?id=70565 Sample of the build log Greetings, I have been building quite a few Wine versions in the past on the same build system (with gcc as the system compiler, and clang available as a secondary compiler), and everything always went fine until Wine v6.16 came out: with the latter, for some (weird) reason, the build system seems to use *both* gcc and clang to compile Wine, and fails as a result... Specifying 'export CC=gcc;export CXX=g++' does not suffice to prevent Wine's build system to wrongly pick up clang, and I must uninstall the latter to get Wine v6.16 to build successfully with gcc... Attached is a short sample of the build log (at the point where it fails too) for you to see. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51694 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek(a)codeweavers.com, | |z.figura12(a)gmail.com Component|-unknown |build-env --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- You'll have to set CROSSCC as well. (Why do we prefer clang? Can we at least try to infer CROSSCC from CC, or is that too hard?) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51694 --- Comment #2 from reserv0(a)yahoo.com --- (In reply to Zebediah Figura from comment #1)
You'll have to set CROSSCC as well.
Yes, just exporting this one as 'gcc' seems to solve the issue...
(Why do we prefer clang? Can we at least try to infer CROSSCC from CC, or is that too hard?)
Why was it changed at all in the first place for the *default* compiler ?... I mean, it's fine to allow the use of a different cross-compiler, but when unspecified, the default system compiler should be used for it... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51694 --- Comment #3 from Alexandre Julliard <julliard(a)winehq.org> --- There's no failure in that log, just a warning. What's the actual failure? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51694 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51694 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla