I had Digikam 0.6.2 installed and working. When I upgraded to 0.7.1, it quit working and the /usr/bin/digikam did not exist. I re-emerged it, and still no executable. I unmerged it and emerged again, and still no executable (all files found from an equery were eithe in /usr/share/docs or /usr/share/locale). Downgrading back to 0.6.2 worked again. Upgrading to unstable 0.7.2 again did not work (removed /usr/bin/digikam). I am now set at 0.6.2 and working well, but ebuilds for 0.7.x seem to be fatally flawed. Reproducible: Always Steps to Reproduce: 1. Emerge digikam-0.6.2 2. Observe functioning application 3. Emerge digikam-0.7.1 4. Observe absence of /usr/bin/digikam or any other executable file. 5. Emerge digikam-0.7.2 6. Observe absence of /usr/bin/digikam Actual Results: Only 0.6.2 works Expected Results: 0.7.1, marked stable, should work. 0.7.2, marked unstable, should still be executable. wintermute wolfger # emerge info Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r7 x86_64) ================================================================= System uname: 2.6.11-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3400+ Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 11 2005, 22:21:42)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.9.5, 1.5, 1.4_p6, 1.7.9-r1, 1.8.5-r3, 1.6.3 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O3 -march=k8 -mtune=k8 -fomit-frame-pointer -fprefetch-loop-arrays -pipe -maccumulate-outgoing-args" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CTARGET="x86_64-pc-linux-gnu" CXXFLAGS="-O3 -march=k8 -mtune=k8 -fomit-frame-pointer -fprefetch-loop-arrays -pipe -maccumulate-outgoing-args" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirrors.tds.net/gentoo http://mirror.datapipe.net/gentoo http://gentoo.chem.wisc.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi aim alsa amd64 arts avi berkdb bitmap-fonts bonobo cdparanoia cdr crypt cups curl directfb dvd dvdr dvdread esd fam fbcon flac font-server foomaticdb fortran gdbm gif gimpprint gphoto2 gpm gstreamer gtk gtkhtml guile imagemagick imlib ipv6 java jikes joystick jp2 jpeg junit kde kdeenablefinal lzw lzw-tiff mad maildir mikmod motif mozilla mp3 mpeg multilib nas ncurses nls ogg oggvorbis opengl oss pam pdflib perl png postgres ppds python qt quicktime readline real samba sdl slang speex ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userlocales vorbis xine xinerama xml xml2 xmms xpm xprint xrandr xv yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, LANG, LC_ALL, LDFLAGS, LINGUAS
You should look at the output during the configure process, it could be that digikam failed to detect one of the dependencies for some reason (libgphoto2, libkexif, libkipi, imlib2, tiff, gdbm). The config.log can also give some hint of what went wrong. (should be in /var/tmp/portage/digikam-0.7.3/work/digikam-0.7.3/config.log during compilation)
It is indeed a problem with imlib2. I do not know why it continues to compile if this is a fatal problem, though. It shouldn't. I have the latest stable version of imlib2: 1.2.0-r2
It does not fail because the build system is meant for cvs, where many modules can be compiled in the same run. So, do you know why it fails to detect imlib2?
Mike, with which use flags is imlib2 built?
(In reply to comment #4) > Mike, with which use flags is imlib2 built? [ebuild R ] media-libs/imlib2-1.2.0-r2 +X -doc +gif +jpeg (-mmx) +nls +png +tiff
Are you still experiencing these problems? I was looking at bugs for digikam as I would like to stabilise 0.7.4 and 0.8.0 is just about to hit ~. I am using digikam on gcc 3.4 and gcc 4 compiled systems and have had no issues. Have you tried rebuilding imlib2?
I previously also had this problem with Amarok, although I never bothered to file a bug for that package after the response I got to this bug. Well, recently I had problems with Cedega, and in searching Google for a solution to that problem, I came across a suggestion to run "python-update". That fixed my Cedega problem, and as of two days ago, Amarok now works for me, and as of two minutes ago, Digikam 0.7.4 now works. I'm not sure if python-update was what fixed this problem for me, but it seems likely.
