This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug plugins/59335] Plugin doesn't build on trunk
- From: "pageexec at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 05 Mar 2014 22:47:18 +0000
- Subject: [Bug plugins/59335] Plugin doesn't build on trunk
- Auto-submitted: auto-generated
- References: <bug-59335-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59335
--- Comment #17 from PaX Team <pageexec at gmail dot com> ---
sure, thanks for fixing the already mentioned ones, i verified that all works
fine for my plugins at least. as a related question, isn't there a better way
than playing this whack-a-mole game with gcc headers vs. plugin headers? as i
understand it, the testsuite doesn't simulate an installed environment for
plugins but there has to be a way to automatically discover new
headers+dependencies that should be exposed to plugins...
PS: i can't reopen this one as i don't seem to have such rights but i'll
comment anyway if i run across something.
PS2: can the $(RESOURCE_H) hunk be backported to the still maintained versions
at least?