[MacPorts] #40266: wine, wine-devel: blacklist clang compilers producing buggy binaries

MacPorts noreply at macports.org
Wed Aug 28 10:16:20 PDT 2013


#40266: wine, wine-devel: blacklist clang compilers producing buggy binaries
---------------------------------------------+-----------------------------
  Reporter:  ionic@…                         |      Owner:  macports-
      Type:  defect                          |  tickets@…
  Priority:  Normal                          |     Status:  new
 Component:  ports                           |  Milestone:
Resolution:                                  |    Version:  2.2.0
      Port:  wine wine-devel wine-crossover  |   Keywords:  haspatch
---------------------------------------------+-----------------------------

Comment (by ionic@…):

 Replying to [comment:9 jeremyhu@…]:
 > If that's the case, you should add gcc-4.2 and apple-gcc-4.2 to
 compiler.blacklist (and I think llvm-gcc fails as well, so you can shorten
 that to *gcc-4.2)

 Blacklisting gcc-4.2 and apple-gcc-4.2 is semantically incorrect, as both
 versions compile sane wine binaries. I want to prefer mp-clang-3.3 over
 (apple-)gcc-4.2 only, not lead other developers and users into thinking
 those compilers won't work. (I.e., (apple-)gcc-4.2 usage should be
 stripped to a minimum, only when really required and new clang versions
 aren't working with a port, to conform with Apple's compiler policy.)

 llvm-gcc on the other hand is breaking wine, yes. Those are already
 blacklisted. :)

-- 
Ticket URL: <https://trac.macports.org/ticket/40266#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list