![]() ![]()
|
I\'ve been trying to build the latest from SVN, and it successfully compiles and installs. However, when I run it, the GUI appears for just a second, then it crashes. When I run it from a terminal I get lots of debugging output, but the interesting line is this one:
amarokapp: symbol lookup error: /usr/lib/libamarok.so.0: undefined symbol: _ZN6TagLib7FileRef19addFileTypeResolverEPKNS0_16FileTypeResolverE The only thing I can think of that might cause problems is that I\'m running on AMD64; there weren\'t any precompiled taglib binaries for my system, so I had to compile them myself. I installed it in /usr/local/lib , and I still have taglib 1.3 installed in /usr/lib, because k3b insists on having it. I\'ve checked the config.log in amarok-svn\'s directory, and it finds taglib in /usr/local and seems to link against it, though, so I\'m not sure what the problem could be... |
![]() KDE Developer ![]()
|
It picks up the wrong TagLib. Remove TagLib 1.3.
--
Mark Kretschmann - Amarok Developer |
![]() ![]()
|
But what should I do about k3b, which insists on having taglib 1.3 installed?
|
![]() KDE Developer ![]()
|
K3B should work just as well with TagLib 1.4. So just force remove 1.3, like --force --nodeps for rpm.
--
Mark Kretschmann - Amarok Developer |
![]() ![]()
|
Well, I force-removed taglib 1.3, then built debs of 1.4 and installed it, and then amarok worked. However, the next time I did an update through Adept, it decided to remove k3b and a couple of kdemultimedia packages because I didn\'t have the taglib they expected. I suppose I\'ll see if I can find the source for them and recompile them so they\'ll expect taglib 1.4...
|
![]() ![]()
|
the addFileTypeResolver stuff was added to taglib 1.4, so the problem is definitely due to taglib 1.3 being used.
|
Registered users: Baidu [Spider], Bing [Bot], Google [Bot], rblackwell