Since their introduction in revision 158247, the tests gcc.dg/plugindir*.c fail on builds not configured with --enable-plugin (see http://gcc.gnu.org/ml/gcc-testresults/2010-04/msg01084.html ). The failure is cc1: error: Plugin support is disabled. Configure with --enable-plugin. i.e., the tests should be skipped for builds not configured with --enable-plugin.
Do the other targets like linux enable plugins by default? If so, once... http://gcc.gnu.org/ml/gcc-patches/2010-04/msg00610.html goes into gcc trunk and gcc-4_5-branch, we can just default darwin to build plugin support as well.
> ... we can just default darwin to build plugin support as well. I think the problem should be addressed (i.e., skip the tests) for any build with plugins not enabled, even if --enable-plugin is the default for the target.
Subject: Re: The tests gcc.dg/plugindir*.c should be restricted to builds configured with --enable-plugin On 15.04.2010 16:41, dominiq at lps dot ens dot fr wrote: > ------- Comment #2 from dominiq at lps dot ens dot fr 2010-04-15 14:41 ------- >> ... we can just default darwin to build plugin support as well. > > I think the problem should be addressed (i.e., skip the tests) for any build > with plugins not enabled, even if --enable-plugin is the default for the > target. on my list.
this is fixed on the trunk
See also pr46902 for other failures of gcc.dg/plugindir*.c.
(In reply to comment #4) > this is fixed on the trunk Any plan to backport the fix to 4.5? or should this pr closed as fixed?
> Any plan to backport the fix to 4.5? or should this pr closed as fixed? No answer after more than one year;-(closing as fixed).