reopen 551200 thanks On 18/10/09 13:01, Matthias Klose wrote: > This option disables the build of the gcjwebplugin. that's not what you > want. The plugin infrastructure is enabled by default.
Hmmm, I have no knowledge about the gcj stuff, maybe there's simply an option clash here. What I can tell for sure, is that the new plugin infrastructure is currently NOT enabled: $ /usr/lib/gcc-snapshot/bin/gcc -fplugin=foo -E - < /dev/null cc1: error: Plugin support is disabled. Configure with --enable-plugin. # 1 "<stdin>" $ /usr/lib/gcc-snapshot/bin/gcc --print-file-name plugin plugin On a locally compiled version (without java support, though), the output is as expected: $ /opt/gcc/20091010-1+plugins/bin/gcc -fplugin=foo -E - < /dev/null cc1: error: Cannot load plugin foo foo: cannot open shared object file: No such file or directory # 1 "<stdin>" $ /opt/gcc/20091010-1+plugins/bin/gcc --print-file-name plugin /opt/gcc/20091010-1+plugins/bin/../lib/gcc/i486-linux-gnu/4.5.0/plugin Since the current debian snapshot explicitly references '--enable-plugin' and given the usual configure option mechanism, '--disable-plugin' looks like the reason for the missing plugin support for me. If the gcjwebplugin support is controlled via the same feature name, this is a (separate) bug and the latter option should be renamed. Maybe this has been done already, and the configure options have to be adjusted accordingly? Regards, Philipp
signature.asc
Description: OpenPGP digital signature
