Matthias Klose wrote:
> On 19.10.2009 19:42, Andrew Haley wrote:
>> Ian Lance Taylor wrote:
>>> Andrew Haley writes:
>>>
Matthias Klose wrote:
> --enable-plugin is used by classpath (part of libjava) and now by GCC
> itself. disabling the build of the gcjwebplugin now disables plugin
On 19.10.2009 19:42, Andrew Haley wrote:
Ian Lance Taylor wrote:
Andrew Haley writes:
Matthias Klose wrote:
--enable-plugin is used by classpath (part of libjava) and now by GCC
itself. disabling the build of the gcjwebplugin now disables plugin
support in GCC as well. Please could the optio
Ian Lance Taylor wrote:
> Andrew Haley writes:
>
>> Matthias Klose wrote:
>>> --enable-plugin is used by classpath (part of libjava) and now by GCC
>>> itself. disabling the build of the gcjwebplugin now disables plugin
>>> support in GCC as well. Please could the option for enabling GCC plugin
>
Andrew Haley writes:
> Matthias Klose wrote:
>> --enable-plugin is used by classpath (part of libjava) and now by GCC
>> itself. disabling the build of the gcjwebplugin now disables plugin
>> support in GCC as well. Please could the option for enabling GCC plugin
>> support be renamed to somethin
Matthias Klose wrote:
> --enable-plugin is used by classpath (part of libjava) and now by GCC
> itself. disabling the build of the gcjwebplugin now disables plugin
> support in GCC as well. Please could the option for enabling GCC plugin
> support be renamed to something like --enable-plugins,
> --
--enable-plugin is used by classpath (part of libjava) and now by GCC itself.
disabling the build of the gcjwebplugin now disables plugin support in GCC as
well. Please could the option for enabling GCC plugin support be renamed to
something like --enable-plugins, --enable-gcc-plugin, --enable-g