I am trying to install media-plugins/kipi-plugin-0.1.5, but the process fails during the configure phase with the following error: checking for libkdcraw in our sources... not found in sources checking for libkdcraw >= 0.1.2... configure: error: libkdcraw library is required by kipi-plugins. !!! ERROR in media-plugins/kipi-plugins-0.1.5: !!! In econf at line 2287 !!! econf failed I am a little confused by this message, because I have libkdcraw already installed, as shown below: # eix libkdcraw [I] media-libs/libkdcraw Available versions: (~)0.1.0 0.1.1 (~)0.1.2 (~)0.1.3 (~)0.1.4 {arts debug elibc_FreeBSD xinerama} Installed versions: 0.1.4(19:58:49 14.5.2008)(-arts -debug -elibc_FreeBSD -xinerama) Homepage: http://www.kipi-plugins.org Description: KDE Image Plugin Interface: a dcraw library wrapper Reproducible: Always Steps to Reproduce: 1. try to emerge media-plugins/kipi-plugins 2. 3. Actual Results: The emerging process fails during configure complaining about missing libkdcraw library Expected Results: Emerge package media-plugins/kipi-plugins successfuly. It seems to be strange that qlist libkdcraw shows no binaries, but only some docs - I am not sure if this is correct. # qlist libkdcraw /usr/share/locale/et/LC_MESSAGES/libkdcraw.mo /usr/share/locale/ca/LC_MESSAGES/libkdcraw.mo /usr/share/locale/nl/LC_MESSAGES/libkdcraw.mo /usr/share/locale/de/LC_MESSAGES/libkdcraw.mo /usr/share/locale/da/LC_MESSAGES/libkdcraw.mo /usr/share/locale/pt/LC_MESSAGES/libkdcraw.mo /usr/share/locale/pa/LC_MESSAGES/libkdcraw.mo /usr/share/locale/el/LC_MESSAGES/libkdcraw.mo /usr/share/locale/sr/LC_MESSAGES/libkdcraw.mo /usr/share/locale/sv/LC_MESSAGES/libkdcraw.mo /usr/share/locale/es/LC_MESSAGES/libkdcraw.mo /usr/share/locale/sk/LC_MESSAGES/libkdcraw.mo /usr/share/locale/sr@Latn/LC_MESSAGES/libkdcraw.mo /usr/share/locale/ms/LC_MESSAGES/libkdcraw.mo /usr/share/locale/uk/LC_MESSAGES/libkdcraw.mo /usr/share/locale/it/LC_MESSAGES/libkdcraw.mo /usr/share/locale/nds/LC_MESSAGES/libkdcraw.mo /usr/share/locale/ja/LC_MESSAGES/libkdcraw.mo /usr/share/locale/is/LC_MESSAGES/libkdcraw.mo /usr/share/locale/th/LC_MESSAGES/libkdcraw.mo /usr/share/doc/libkdcraw-0.1.4/AUTHORS /usr/share/doc/libkdcraw-0.1.4/ChangeLog /usr/share/doc/libkdcraw-0.1.4/README /usr/share/doc/libkdcraw-0.1.4/NEWS
HI Tomas, please try re-merging of the libkdcraw package. If it doesn't help, please post full build logs of the libkdcraw as it is indeed broken on your system.
Created attachment 153167 [details] emerge log of the libkdcraw package
Re-emerging of the libkdcraw package did not help. But when looking through the build log thoroughly, I found these lines: -- libkdcraw configure results ------------------- -- lcms found..................... NO libkdcraw needs Lcms library. You need to install the lcms development package. Lcms website is at http://www.littlecms.com So I tried to emerge the media-libs/lcms package and re-emerged the libkdcraw package again. After that the kipi-plugins packages builds correctly.
.
Dear KDE team, there is obviously a missing dep on media-libs/lcms and also either error in upstream's configure script or kde eclass not dealing with econf failures. Please fix0r :).
(In reply to comment #5) > [...] also either error in upstream's configure script or kde eclass not > dealing with econf failures. Yes, upstream's configure script doesn't return error when it fails. econf dies on its own so the '|| die' for econf in kde.eclass isn't even necessary.
Created attachment 162639 [details, diff] Add dependency on media-libs/lcms to media-libs/libkdcraw Patch to add dependency on media-libs/lcms to media-libs/libkdcraw attached, which fixes the problem for me on Linux cube 2.6.25-gentoo-r6 #1 Mon Jul 7 12:49:30 PDT 2008 ppc 7400, altivec supported PowerMac5,1 GNU/Linux
Just here to say that this bug occurred again when adding kipi plugins support to gwenview. emerging lcms then reemerging libkdcraw fixed my problem too.
I've added a hard depend on media-libs/lcms to libkdcraw-0.1.4, leaving this bug open for the configure script issue..
Okey, the dependency is in main tree since 0.1.4 from what i can see. So this bug is fixed.