Undefined symbol warning_at when loading gcc-python-plugin

[David Narvaez]

On Fri, Sep 14, 2012 at 12:18 AM, Ian Lance Taylor <iant@google.com> wrote:
> Your plugin is expecting a GCC built with C, but you have a GCC built
> with C++.  GCC 4.8 will require C++.  In GCC 4.7 it is the default but
> is optional.  Quick workaround to build GCC 4.7 with C: configure GCC
> 4.7 with --diable-build-poststage1-with-cxx.  Otherwise you will need
> to build your plugin with C++.

Thanks. Just to get the whole picture: how come cc1 is able to load
this plugin in x86?

David E. Narvaez