All,

  Amarok is again building on Arch. However, the build did uncover what are
probably several bugs in the amarok/amarok/src/mediadevice code. I was able to
build amarok with the following enabled. All options turned OFF appear to be
bugs in the code or in the CMake files that control the build for the individual
options:

  CXXFLAGS="${CXXFLAGS} -I/usr/include/ruby-1.9.1 -fpermissive" \
  cmake ${srcdir}/${pkgname#*-} \
    -DCMAKE_INSTALL_PREFIX=${TDEDIR} \
    -DCMAKE_VERBOSE_MAKEFILE=ON \
    -DWITH_LIBVISUAL=ON \
    -DWITH_KONQSIDEBAR=ON \
    -DWITH_XINE=ON \
    -DWITH_YAUAP=OFF \
    -DWITH_IPOD=ON \
    -DWITH_IFP=ON \
    -DWITH_NJB=ON \
    -DWITH_MTP=OFF \
    -DWITH_RIOKARMA=OFF \
    -DWITH_DAAP=OFF \
    -DBUILD_ALL=ON

  I don't know what limitations this imposes on Amarok, but 'yauap', 'mtp',
'riokarma' and 'daap' all failed with errors similar to:

/build/src/amarok/amarok/src/mediadevice/daap/mongrel/http11/http11.c
/build/src/amarok/amarok/src/mediadevice/daap/mongrel/http11/http11.c:5:18:
fatal error: ruby.h: No such file or directory

  That's with the -I/usr/include/ruby-1.9.1 set....

  But, it's working. Do we want a bug on the remaining mediadevice issues?

-- 
David C. Rankin, J.D.,P.E.