Why can configure.compiler be cc or gcc?

[Jeremy Huddleston Sequoia]

Yes, if building from source, we should error out if (/usr/include/stdlib.h doesn't exist) or ((the xcode version is "none" or "") and (OS is macosx)).

--Jeremy

On Nov 4, 2013, at 16:50, Ryan Schmidt <ryandesign at macports.org> wrote:

> 
> 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. 
> 
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20131104/dafd36db/attachment-0001.p7s>