Why can configure.compiler be cc or gcc?

[Ryan Schmidt]

On Nov 4, 2013, at 18:45, Jeremy Huddleston Sequoia wrote:

> I think those are there for legacy reasons and to support non-OS X installs.
> 
> If Xcode isn't present, the default compiler is cc:
> 
> proc portconfigure::get_compiler_fallback {} {
>    global xcodeversion macosx_deployment_target default_compilers
>    if {[info exists default_compilers]} {
>        return $default_compilers
>    } elseif {$xcodeversion == "none" || $xcodeversion == ""} {
>        return {cc}
>    } …
> }

Ok, so that’s the problem this user was experiencing. He didn’t have Xcode installed.

So we need to do a better job in the configure script and in the installer pkg preflight of detecting the presence of Xcode and its command line tools before allowing MacPorts to be installed.