------- Comment #2 from joseph at codesourcery dot com 2009-05-02 09:34 ------- Subject: Re: New: gcc does not install appropriate plugin headers
On Sat, 2 May 2009, bradh at frogmouth dot net wrote: > Writing a plugin requires use of a range of headers (such as gcc-plugin.h) > which are not installed. Here is an example: > > $ /opt/gccsvn/bin/gcc -v --save-temps -Dmy_gcc_plugin_EXPORTS -fPIC -o > dumb_plugin-orig.c.o -c dumb_plugin-orig.c You'd need to use a -I option pointing to the plugin headers install directory anyway; they aren't going to be installed in the default search path, since they are headers for the host, not the target, and depend on the exact GCC configuration, and multiple differently configured copies of GCC for different targets can be installed in the same prefix. But it doesn't look like the patch to install plugin headers under libsubdir/plugin/include has yet been reviewed/approved. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40004
