Authors of gimp recognize need to link this plugin explicitly with -lX11. This is done via special variable LIBSCREENSHOT that should contain both -L/usr/X11R6/lib and -lX11. It doesn't for unknown reason. The fix is to explicitly set LIBSCREENSHOT variable to '-L/usr/X11R6/lib -lX11' instead of $X_LIBS in configure.in and recreate configure. Patches will follow. Reproducible: Always Steps to Reproduce: 1. ebuild gimp Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r30, 2.4.25) ================================================================= System uname: 2.4.25 i686 AMD Athlon(tm) Gentoo Base System version 1.4.2.8 Autoconf: sys-devel/autoconf-2.59 Automake: sys-devel/automake-1.7.8 ACCEPT_KEYWORDS="x86 ~x86" (...) USE="3dnow alsa apm avi berkdb bonobo cdr crypt cups dga foomaticdb gd gdbm ggi gif gpm guile imlib java jpeg justify kde libg++ libwww mad mbox mikmod mmx mpeg ncurses oggvorbis opengl oss pdflib png python qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tetex truetype x86 xmms xv zlib"
Created attachment 28732 [details, diff] Fixes linking to -lX11 in screenshot plugin
Created attachment 28733 [details, diff] Adds gimp-2.0.0-screenshotX11.patch to gimp-2.0.0.ebuild Adds gimp-2.0.0-screenshotX11.patch to .ebuild and and recreates configure script via autoconf line in src_compile().
i'm not convinved this is a problem, works just fine here. You only need to have X in your USE flags, which you don't have. I suppose it doesn't break the building process ? ps. and don't just skip parts of emerge info, we want it all in every report. You don't have to filter it for us on what you deem important.
Having '+X' in USE is unnacteptable solution. I don't want hundrets of gui lines of code build (like aumix) just to make gimp ebuild work. Force this via internal methods instead of fail-prone user side. Users always have crazy ideas and gentoo should work properly in as much of those situations as possible. Making users add X to USE just because "everyone" has this is _not_ a good idea.
It's an X specific extension, so it makes perfect sense as part of the X flag. I don't see the problem there.
You are completly right. This bug is invalid.
