Re: Help with a syntax error from an autoreconf'ed configure script

[wferi@niif.hu]

John Scott <jscott@posteo.net> writes:

> binutils/libiberty/configure: line 2911: syntax error near unexpected token `PLUGIN_OPTION'
> binutils/libiberty/configure: line 2911: `GCC_PLUGIN_OPTION(PLUGIN_OPTION)'
>
> This seems bizarre. Why would autoreconf produce a script with a syntax
> error, or is dash not robust enough to use what construct it's trying
> in the script?

I guess GCC_PLUGIN_OPTION (which is meant to be an Autoconf/m4 macro) is
not defined in this case for some reason, so it's passed verbatim into
the configure script by Autoconf and later misinterpreted by the shell
as a function definition.  Try to find out why it (and PLUGIN_OPTION)
isn't defined in the failing case; it should be provided by
config/gcc-plugin.m4, I think.
-- 
Regards,
Feri