compiler.whitelist and compiler installation side-effects

[Ryan Schmidt]

Let's keep the discussion on the mailing list.

On Sep 20, 2015, at 12:27 PM, René J.V. Bertin wrote:

> BTW, how difficult would it be to implement a range filter for blacklisting older  macports-clang versions, or newer versions (3.7 doesn't build on OS X 10.6) :
> 
> {macports-clang < 3.4}
> {macports-clang > 3.6}

Range filtering is already included in the compiler_blacklist_versions portgroup. An example is given in the portgroup:

# Blacklist only clang build numbers greater than or equal to 421.11.66 but less than 444:
# compiler.blacklist-append {clang >= 421.11.66 < 444}

Trying to use "macports-clang" as the compiler name is not supported because that relies on the user having selected a version of MacPorts clang using "port select", and ports are not allowed to rely on the user having done that.

Looks like 3.5 and later require libc++ to exist; it doesn't exist on 10.6 unless the user puts it there per the instructions in the LibcxxOnOlderSystems wiki page.