[Bug 51694] New: Wine v6.16 build fails when both gcc and clang are available on the build system

[WineHQ Bugzilla]

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: [e-mail]
          Reporter: [e-mail]
      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.

[Bug 51694] Wine v6.16 build fails when both gcc and clang are available on the build system

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51694

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail],
                   |                            |[e-mail]
          Component|-unknown                    |build-env

--- Comment #1 from Zebediah Figura  ---
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?)

[Bug 51694] Wine v6.16 build fails when both gcc and clang are available on the build system

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51694

--- Comment #2 from [e-mail] ---
(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...

[Bug 51694] Wine v6.16 build fails when both gcc and clang are available on the build system

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51694

--- Comment #3 from Alexandre Julliard  ---
There's no failure in that log, just a warning. What's the actual failure?

[Bug 51694] Wine v6.16 build fails when both gcc and clang are available on the build system

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51694

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 51694] Wine v6.16 build fails when both gcc and clang are available on the build system

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51694

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
     Ever confirmed|0                           |1