On Dec 9, 2017, at 11:31, Ken Cunninghamwrote: >> >> But come to think of it, if the commandline configure.compiler override is >> not a glitch in my local install it also means that this concern is moot. >> > > > As an aside, I make extensive use of the command line configure.compiler > override and also the default_compiler setting in macports.conf being able to > overcome all compiler blacklisting and setting done in the Portfile. It is > often needed / useful / required.
It should be used as a developer debugging tool. It should never be required for end users to install a port. If it is, it is a bug in the port's or its dependencies' compiler selection / blacklisting. > I would humbly request we do not change this behaviour, as it is very useful.
