#52537: hatari - fix for build on Snow Leopard without Xcode 4.2 --------------------------------------+--------------------------------- Reporter: ken.cunningham.webuse@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: hatari | --------------------------------------+--------------------------------- Comment (by larryv@…): Replying to [comment:11 ken.cunningham.webuse@…]:
In the end I forced it to macports-clang-3.7 or newer, as most people would / should likely have that clang version on Snow Leopard.
This is not a safe assumption to make. Given that 3.7 is (a) not in the default fallback list for Xcode 3.2 and (b) requires manual bootstrapping, 3.4 is almost certainly more likely to be present.
Even when I blacklisted { clang < 211 } the system kept choosing xcode's clang. I tried bumping the number up to 500, and it '''still''' chose xcode's clang, even though i have macports-clang-3.7 installed. Only when I blacklisted all clang did it ignore xcode's clang
This doesn’t sound right. Did you add the compiler_blacklist_versions-1.0 portgroup? Base doesn’t support version blacklisting on its own.
and then it started installed macports-clang-3.4 (even though macports-clang-3.7 was there).
MacPorts does not just use whatever compiler happens to be there. It follows the combination of blacklist/whitelist/fallback list, which is deterministic.
I understand in a rudimentary way how the logic for this goes, but if you're going to force a clang install on SL, it might as well be 3.7.
This isn’t the place for this conversation, but I disagree because 3.7 requires manual bootstrapping. I suspect you just didn’t use compiler_blacklist_versions-1.0. If you add that, blacklisting `{clang < 211}` should work fine. -- Ticket URL: <https://trac.macports.org/ticket/52537#comment:12> MacPorts <https://www.macports.org/> Ports system for the Mac operating system