Bug 210094 – media-gfx/gimp-2.4.2 not linked without jpeg flag

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Aleksey 2008-02-14 09:02:52 UTC]

i emerge gimp 2.4.2
without jpeg flag emerge fail (no meaning message from emerge)
with jpeg flag all ok

need make some usefull message from emerge

Reproducible: Always

Steps to Reproduce:
1. disable flag jpeg in make.conf
2. emerge gimp
3. 

Actual Results:  
not emerged
link error, unreferenced functions


i686-pc-linux-gnu-gcc -O2 -march=pentium3m -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -o jpegqual jpeg-quality.o jpegqual.o -pthread  /u
sr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libpango-1.0.so /usr/lib/libcairo.so /usr/lib/libgobject-2.0.so
 /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libgthread-2.0.so -lrt /usr/lib/libglib-2.0.so
jpegqual.o: In function `analyze_file':
jpegqual.c:(.text+0x4bd): undefined reference to `jpeg_std_error'
jpegqual.c:(.text+0x4ff): undefined reference to `jpeg_CreateDecompress'
jpegqual.c:(.text+0x511): undefined reference to `jpeg_stdio_src'
jpegqual.c:(.text+0x522): undefined reference to `jpeg_read_header'
jpegqual.c:(.text+0x5c1): undefined reference to `jpeg_destroy_decompress'
jpegqual.c:(.text+0x5ed): undefined reference to `jpeg_destroy_decompress'
collect2: ld returned 1 exit status
make[3]: *** [jpegqual] Error 1
make[3]: Leaving directory `/var/tmp/portage/media-gfx/gimp-2.4.2/work/gimp-2.4.2/plug-ins/jpeg'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/media-gfx/gimp-2.4.2/work/gimp-2.4.2/plug-ins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/media-gfx/gimp-2.4.2/work/gimp-2.4.2'
make: *** [all] Error 2

[Comment 1 Jakub Moc (RETIRED) 2008-02-14 09:04:36 UTC]

Has nothing to do with portage.

[Comment 2 Jakub Moc (RETIRED) 2008-02-14 09:06:11 UTC]

*** This bug has been marked as a duplicate of bug 191916 ***