Current AmaroK depends on taglib version 1.4. KDE ships with taglib 1.3 in its /usr/kde/3.5/ directory. Manually emerging taglib installs headers in the usual /usr/include directory. This makes AmaroK only checking it's kde headers, bailing out as it finds the wrong version i e 1.3. The ebuild needs to look in the right paths to compile.
Reopen with config.log attached, exact amarok version and emerge --info. Nothing bails out here.
Created attachment 83695 [details] emerge build.log With taglib installed a have two versions of taglib-config installed/ The KDE supplied ver 1.3 in /usr/kde/3.5/bin/taglib-config The taglib 1.4 emerged version in /usr/bin/taglib-config The build log clearly shows that the amarok configure script checks the wrong one, ie 1.3 in /usr/kde/3.5/bin
Created attachment 83696 [details] emerge --info
removing the /usr/kde/3.5/bin/taglib-config makes the configure script find the /usr/bin/taglib-conf (ie 1.4) which prevents amarok from bailing out.
Uhm no, I meant config.log (found in /var/tmp/portage/amarok...)
Reopen with "equery b /usr/kde/3.5/bin/taglib-config", please...
equery b /usr/kde/3.5/bin/taglib-config [ Searching for file(s) /usr/kde/3.5/bin/taglib-config in *... ] Gave unfortunately nothing at all as output.
(In reply to comment #7) > equery b /usr/kde/3.5/bin/taglib-config > [ Searching for file(s) /usr/kde/3.5/bin/taglib-config in *... ] > > Gave unfortunately nothing at all as output. Yeah, because kde (as distributed by Gentoo) doesn't install any such binary. It's bogus, shouldn't be there, we didn't install it. Marking this INVALID.
