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

MacPorts noreply at macports.org
Wed Aug 28 08:13:26 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:1 egall@…]:
 > If you're using `compiler.whitelist`, it will make it so ''only'' those
 compilers can be used, making the blacklisting mostly redundant. Perhaps
 you want `compiler.fallback-append` instead?

 Yes, I do! Thanks and sorry, changed that locally. New patch after the
 next issue has been discussed.



 Replying to [comment:3 ryandesign@…]:
 > Presumably wine-crossover is also affected?

 Oh, that's compiling from source, too. Then... yes and no. wine-crossover
 is using compiler.whitelist gcc-4.2 apple-gcc-4.2 which is fine for now
 (it's not including the winemac.drv yet, thus can use FSF GCC) and clang
 is automatically blacklisted, but it should be made consistent with the
 other wine ports. So patching is in order as well.



 > `compiler.fallback` could just be set to macports-clang-3.3; no reason
 to list older versions since we don't want them.
 The general idea was to allow/prefer both mp-clang-3.2 and mp-clang-3.3,
 so as to not make wine(-devel/-crossover) pull in mp-clang-3.3, if mp-
 clang-3.2 is already installed on the user's system. Will `compiler.fall
 macports-clang-3.3` automatically take care of using mp-clang-3.2 if
 already available and ignore mp-clang-3.3? From the MP source, it looked
 like this isn't the case.

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


More information about the macports-tickets mailing list