Re: patch to add AES intrinsics to gcc

On Fri, 23 Aug 2013, Bernhard Fröhlich wrote:
> lang/gcc42 is on the list of ports that have USE_GCC=any. So you would 
> need to fix it first to be able to compile it with clang 3.3 from base.

I don't think so. :-)

You can install lang/gcc which builds just fine with clang, and
then use lang/gcc to build lang/gcc42.

In fact, if you have a system without GCC in the base, this should 
happen automatically when you build lang/gcc42.  Does this not work?


> We are not trying to build everything with lang/gcc but just the ports 
> that have USE_GCC=any in their Makefile. 

...and those that have USE_GCC=yes in their Makefile.

The difference between USE_GCC=yes and USE_GCC=any is that the later 
is there to support the transition period and uses /usr/bin/gcc if 
present.


Personally, I would stop relying on /usr/bin/gcc (even if present)
and use the lang/gcc port in all cases.  That reduces the number of
different scenarios to test, but will pull in lang/gcc in some more 
cases and may meet some resistance therefore.

Gerald