on configure: ... checking for GDK_PIXBUF - version >= 0.2.5... yes Unknown library `libglade' Unknown library `libglade' checking how to run the C preprocessor... gcc -E ... which should be: GNOME_CFLAGS=`gnome-config --cflags gnomeui libglade` GNOME_LIBS=`gnome-config --libs gnomeui libglade` --------- on build: test.c:3:25: glade/glade.h: No such file or directory test.c: In function `main': test.c:11: `GladeXML' undeclared (first use in this function) test.c:11: (Each undeclared identifier is reported only once test.c:11: for each function it appears in.) test.c:11: `xml' undeclared (first use in this function) test.c:27: warning: assignment makes pointer from integer without a cast make[2]: *** [test.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/gtk-engines-eazel-0.3-r1/work/eazel-engine-0.3' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gtk-engines-eazel-0.3-r1/work/eazel-engine-0.3' make: *** [all-recursive-am] Error 2 !!! ERROR: x11-themes/gtk-engines-eazel-0.3-r1 failed. !!! Function gtk-engines2_src_compile, Line 103, Exitcode 2 !!! make failed --------- tomcat root # emerge -pv libglade ... [ebuild R ] gnome-base/libglade-2.0.1 -doc +nls --------- Might it need libglade-0.17-r6.ebuild? Reproducible: Always Steps to Reproduce: 1.: emerge =gtk-themes-1.0 (without using GNOME)
emerge =libglade-0.17-r6 solves it so just an add to DEPEND, I assume
There are comments re: this in gtk-engines-eazel-0.3. From CVS log, looks like they were added by leonardop, but some time ago. Does this mean that gtk-engines-eazel-0.3 never compiled unless the user happened to have libglade installed ? (I think I hear Spider rumbling now) Suggestions ?
from -r1 ebuild : # This one needs the capplet stuff from gnomecc-1.4. Some # tests also need libglade, but it is a heavy dep, so dont # know if we should rather disabled the tests...
brings me to to the question: How many packages are there which have could have a manually invoked test (=invoked via ebuild)? If there are enough packages I would propose a global USE-flag "test", so user can decide if they want to enable test for their software and are willing to maybe emerge also a few extra-deps for it.
It's like debug everywhere, a lot of work and little gain for the casual user. You can do it yourself if you like. Tests usually are of little importance to the general user and there for developer purposes only (and they don't get installed). But this is a bit offtopic really.
to close this bug I would suggest to bump to -r2 with disabled tests, so the next user with this constellation doesn't run into the same error. (I tried myself but configure/make don't seem to listen to --disable-gtktest/--disable-gdk-pixbuftest, although stated in --help :/)
Those are other tests. I worked around it by replacing the test with a 0 returning piece of code. Please test.
