svn commit: r517725 - head/lang/gcc9

[Tobias Kortkamp]

On Sun, Dec 22, 2019 at 12:00:21PM +1000, Gerald Pfeifer wrote:
> On Sat, 14 Dec 2019, Tobias Kortkamp wrote:
> >> Log:
> >>   Backport 517206 | gerald | 2019-11-10 from lang/gcc10-devel, which already
> >>   landed in lang/gcc9-devel as r517355 | gerald | 2019-11-13.
> >>   
> >>     Add a new option PLUGINS that enables GCC's plugin framework. This is off
> >>     by default for now, but something to possibly make the default after a bit
> >>     of settling.
> > when can we enable PLUGINS by default?
> 
> Why would you like to see that?  (Genuine question!)
> 
> We could make this change in the next couple of days as far as 
> lang/gcc10-devel and perhaps lang/gcc9-devel are concerned. With 
> lang/gcc9 I tend to be more conservative by default, hence the 
> question above.

It unlocks the ability to package GCC plugins (like the one in
security/afl++) without custom builds of GCC.  I would like to
enable afl++'s GCC option by default, but a prerequisite of that
is that PLUGINS is turned on by default in lang/gcc9.

Are there any downsides in enabling PLUGINS by default?

(Also see https://bugs.freebsd.org/242644)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20191222/68125482/attachment.sig>