[MacPorts] #40266: wine, wine-devel: blacklist clang compilers producing buggy binaries
MacPorts
noreply at macports.org
Wed Aug 28 09:09:06 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 jeremyhu@…):
Replying to [comment:4 ionic@…]:
> Replying to [comment:3 ryandesign@…]:
> > `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.
Yes, unfortunately base isn't smart enough to pick the first installed
fallback. It picks the first available (possibly available after
installing it) fallback.
So since macports-clang-3.3 is already in compiler.fallback with base 2.2,
the compiler.whitelist line is actually unnecessary =).
> Btw, there's a new crossover-sources build (12.5.0) available which
includes wine 1.6, so I'd rather bump + include the compiler fixes at
once?
I still haven't gotten around to testing 12.5.0. Feel free to bump it if
it works for you. wine 1.6 doesn't work for me, so I haven't checked if
crossover fixed that or not in 12.5.
--
Ticket URL: <https://trac.macports.org/ticket/40266#comment:6>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list