On Mon, 26 Mar 2012, David Malcolm wrote:

> Presumably a fix would be for the plugin's configuration phase to have a
> test that tries to build a test plugin and run it, first building with a
> C compiler, then a C++ compiler, and decides what compiler the real
> plugin should be built with accordingly.

We've previously discussed providing some generic configure / build 
support for plugins (standard autoconf macros intended for use in a 
plugin's build system, for example).  If in future plugins are supported 
on Windows hosts (or any other hosts that lack a -rdynamic equivalent) 
then such generic support will be increasingly useful because of the need 
to link plugins on such hosts against a shared library or libraries that 
contain most of GCC.

-- 
Joseph S. Myers
jos...@codesourcery.com

Reply via email to