On Jul 22, 2011, at 11:20 PM, Ryan Schmidt wrote: > > On Jul 22, 2011, at 20:48, [email protected] wrote: > >> Revision: 81005 >> http://trac.macports.org/changeset/81005 >> Author: [email protected] >> Date: 2011-07-22 18:48:35 -0700 (Fri, 22 Jul 2011) >> Log Message: >> ----------- >> Add a 'cc' compiler option for the system default compiler (as opposed to >> gcc which is the system default gcc compiler) > > Remind me again why do we have either of these values? I thought the point of > configure.compiler was to be specific about what compiler we want to use.
Well, 'cc' is there for the same reason that 'gcc' is there, but with the knowledge that gcc no longer has a monopoly on compilation. cc can be the sun compiler, clang, gcc, or any other compiler out there. Yes, we want to have *specific* values used as defaults in portconfigure.tcl, but we use 'gcc' as a fallback for the default if we can't determine the XCode version (such as on puredarwin, BSD, etc). This fallback should change to 'cc', but I wanted to test the waters first to determine if we should remove the 'gcc' option at the same time or just leave it in there for compatibility. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
