On Nov 1, 2011, at 17:38, [email protected] wrote:
> Revision: 86719
> http://trac.macports.org/changeset/86719
> Author: [email protected]
> Date: 2011-11-01 15:38:27 -0700 (Tue, 01 Nov 2011)
> Log Message:
> -----------
> Add support for versioned clang and the port selected gcc in
> configure.compiler
>
> Modified Paths:
> --------------
> trunk/base/src/port1.0/portconfigure.tcl
>
> Modified: trunk/base/src/port1.0/portconfigure.tcl
> ===================================================================
> --- trunk/base/src/port1.0/portconfigure.tcl 2011-11-01 22:38:17 UTC (rev
> 86718)
> +++ trunk/base/src/port1.0/portconfigure.tcl 2011-11-01 22:38:27 UTC (rev
> 86719)
> @@ -203,6 +203,7 @@
> clang { set name "Mac OS X clang" }
> apple-gcc-4.0 { set name "MacPorts Apple gcc 4.0" }
> apple-gcc-4.2 { set name "MacPorts Apple gcc 4.2" }
> + macports-gcc { set name "MacPorts gcc (port select)" }
> + macports-clang { set name "MacPorts clang (port select)" }
When would we ever want a port to use the compiler the user has selected? We've
always made a big deal about how "port select" is for a user's convenience only
and would never be intentionally used by any port.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
