RFC: Support for future compilers in base

Jeremy Huddleston Sequoia jeremyhu at macports.org
Fri Feb 15 01:10:30 PST 2013

On Feb 15, 2013, at 12:51 AM, Lawrence Velázquez <larryv at macports.org> wrote:

> On Feb 15, 2013, at 3:10 AM, Jeremy Huddleston Sequoia <jeremyhu at macports.org> wrote:
>> I'd like to update base trunk such that future versions of clang, dragonegg, and gcc "just work", so we don't need to wait for newer versions of base to depend on newer compilers.
>> I've taken a first pass at portconfigure.tcl and here is a patch.  Comments?  Concerns?
> Unless I'm not seeing it, I think you need to add a mechanism to prevent garbage input like
>    configure.compiler macports-gcc-3.14
> Currently that would just match the default case in the configure_start switch, but I guess now you'll have to check for the (nonexistent) "gcc314" port?

That is the entire point of this patch.  macports-gcc-3.14 is perfectly valid and should result in a dependency on gcc314.  Of course the developer would then see a lint error about an unknown port just like they would see if they added 'depends_build port:gcc314' to the Portfile.


More information about the macports-dev mailing list