patch to add AES intrinsics to gcc

[Warner Losh]

Can all such ports be identified with a ports build run in a special chroot without FreeBSD's FCC installed?

Sent from my iPad

On Aug 25, 2013, at 7:41 PM, Gerald Pfeifer <gerald at pfeifer.com> wrote:

> On Fri, 23 Aug 2013, Volodymyr Kostyrko wrote:
>> I object. Many ports that compiles perfectly on gcc 4.2.1 can't be 
>> compiled with lang/gcc. I checked this once and the number of ports 
>> that require strictly gcc 4.2.1 was bigger for me then number of 
>> ports that can't be compiled with clang but fill fine on lang/gcc.
>> 
>> I'll gonna recheck whether lang/gcc42 is sufficient for them. But I 
>> have that bad feeling...
> 
> If there are ports that use USE_GCC=any and do not build with
> lang/gcc, these should have USE_GCC=4.2 -- without a '+'! --
> not USE_GCC=any.
> 
> It'll be great if you can fix any such port.
> 
> Gerald
> _______________________________________________
> freebsd-toolchain at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
> To unsubscribe, send any mail to "freebsd-toolchain-unsubscribe at freebsd.org"