Amarok 2.4.0.90 (2.4.1 beta 1 ?) fails after build

[Lydia Pintscher]

On Tue, Mar 22, 2011 at 20:28, Thad Humphries <thad.humphries at gmail.com> wrote:
> I recently upgraded from SuSE 11.3 to 11.4.  That went well enough, so I
> thought I'd try building and installing Amarok 2.4.1 beta 1
> (http://mail.kde.org/pipermail/amarok/2011-March/032603.html). Most
> especially, I wanted to apply Daniel Faust's fix for various artists as the
> bug keeps me from using my iPod with Amarok
> (http://mail.kde.org/pipermail/amarok/2011-February/032586.html).  (I also
> dream that some day podcasts will install to my iPod, but for now gpodder
> handles that chore.)
>
> (BTW, the 2.4.1 beta 1 tarball download amarok-2.4.0.90.tar.bz2. I guess
> that's what I'm supposed to use.)
>
> I followed the build instructions (http://amarok.kde.org/wiki/Compiling),
> modifying  instructions (http://amarok.kde.org/wiki/Compiling) before
> running make. After a few attempts and pauses to install optional packages
> and additional devel RPMs, the build completed and I ran install (as root).
> However when I try to run amarok I get the following error dialog:
>
> Amarok could not find any collection plugins. It is possible that Amarok is
> installed under the wrong prefix, please fix your installation using:
> $ cd /path/to/amarok/source-code/
> $ su -c "make uninstall"
> $ cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` && su -c "make
> install"
> $ kbuildsycoca4 --noincremental
> $ amarok
> More information can be found in the README file. For further assistance
> join us at #amarok on irc.freenode.net.
>
> Note that the compiling instructions (http://amarok.kde.org/wiki/Compiling)
> say nothing about running kbuildsycoca4.  No matter, Amarok fails either way
> (kbuildsycoca4 shows many errors trying to read stuff in my old /opt/kde3
> directory, but god knows if that can be safely removed).
>
> What gives?  Any ideas on a fix?  I really need the various artists fix.

Did you read the note on http://amarok.kde.org/wiki/Download:Source ?
This is very likely your problem.


Cheers
Lydia

-- 
Lydia Pintscher
Amarok community manager
kde.org - amarok.kde.org - kubuntu.org
claimid.com/nightrose