Im trying to emerge monodevelop, and vte-sharp is a dependency but something weird is happening cause he isnt finding the gtk include files. i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/include/freetype2 -I../.. -g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wshadow -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings -MT generated.lo -MD -MP -MF .deps/generated.Tpo -c generated.c -fPIC -DPIC -o .libs/generated.o In file included from generated.c:4: /usr/include/vte/vte.h:28:18: glib.h: No such file or directory /usr/include/vte/vte.h:29:25: pango/pango.h: No such file or directory /usr/include/vte/vte.h:30:21: gtk/gtk.h: No such file or directory
Downgrade your version of vte - 0.11.16 does something weird with the pkgconfig file, and vte-sharp hasn't been updated yet to deal with it - that is the workaround for now.
gtk-sharp/vte/glue/Makefile.am needs $(GTK_CFLAGS) added to INCLUDES, that fixes it. There might be a bug in the recent version of vte not telling pkg-config all of its dependencies.
Created attachment 75680 [details] vte-sharp-2.4.0-r1.ebuild new fixed ebuild (stupid eclasses)
Created attachment 75681 [details, diff] files/vte-sharp-gtk_fix.patch patch to fix the problem
PEASE CHANGE IT TO _FIXED_ and add to the portage
@all: I have a better fix for this via a small addition to the gtk-sharp-component.eclass which will make things a lot nicer. I'm on vacation currently, but i'll hopefully get to this within a week or so.
This is actually a vte bug, see that the vte.pc file was reverted in gnome CVS (http://cvs.gnome.org/viewcvs/vte/vte.pc.in?rev=1.12&view=markup). I'm trying to get in touch with the gnome herd on IRC, i'll open a bug with them tonight if I don't manage to get in touch with them.
Can everyone please try with the recently updated vte version and report if they still have problems? Thanks.
(In reply to comment #8) > Can everyone please try with the recently updated vte version and report if > they still have problems? Thanks. > I just tested the most recent vte-0.11.16-r1 and it looks like vte-sharp now compiles fine (at least vte-2.6.0).
Ok, marking this FIXED, feel free to re-open if necessary.