Date: Sun, 25 Aug 2013 21:38:55 -0600 From: Warner Losh <wlosh@bsdimp.com> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: "toolchain@freebsd.org" <toolchain@freebsd.org>, Volodymyr Kostyrko <c.kworr@gmail.com>, John-Mark Gurney <jmg@funkthat.com>, "current@freebsd.org" <current@freebsd.org> Subject: Re: patch to add AES intrinsics to gcc Message-ID: <C2E48141-EA7A-48EF-AAF5-974DFA09FE20@bsdimp.com> In-Reply-To: <alpine.LNX.2.00.1308260329190.3920@trevally.site> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <CAE-m3X324rbdP_C=az4eO-EkMcR-yFAeRG7S4q%2BMUsnMezGddw@mail.gmail.com> <521751AF.6040905@gmail.com> <alpine.LNX.2.00.1308260329190.3920@trevally.site>
next in thread | previous in thread | raw e-mail | index | archive | help
Can all such ports be identified with a ports build run in a special chroot w= ithout FreeBSD's FCC installed? Sent from my iPad On Aug 25, 2013, at 7:41 PM, Gerald Pfeifer <gerald@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=20 >> compiled with lang/gcc. I checked this once and the number of ports=20 >> that require strictly gcc 4.2.1 was bigger for me then number of=20 >> ports that can't be compiled with clang but fill fine on lang/gcc. >>=20 >> I'll gonna recheck whether lang/gcc42 is sufficient for them. But I=20 >> have that bad feeling... >=20 > If there are ports that use USE_GCC=3Dany and do not build with > lang/gcc, these should have USE_GCC=3D4.2 -- without a '+'! -- > not USE_GCC=3Dany. >=20 > It'll be great if you can fix any such port. >=20 > Gerald > _______________________________________________ > freebsd-toolchain@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to "freebsd-toolchain-unsubscribe@freebsd.or= g"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C2E48141-EA7A-48EF-AAF5-974DFA09FE20>