[Bug other/40004] gcc does not install appropriate plugin headers

2009-05-08 Thread bradh at frogmouth dot net


--- Comment #3 from bradh at frogmouth dot net  2009-05-08 07:58 ---
Looks like the install is now dealing with this.


-- 

bradh at frogmouth dot net changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40004



[Bug other/40004] gcc does not install appropriate plugin headers

2009-05-02 Thread bradh at frogmouth dot net


--- Comment #1 from bradh at frogmouth dot net  2009-05-02 07:23 ---
Created an attachment (id=17791)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17791action=view)
.i of trivial example

Source was only one line:
#include gcc-plugin.h


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40004



[Bug other/40004] gcc does not install appropriate plugin headers

2009-05-02 Thread joseph at codesourcery dot com


--- 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