|
hello all!
I\'ve tried amaroK 1.3.8, and fell in love with it! however, because i had problems with my ipod (i read somewhere on these forums that 4th gen ipods and older versions of amaroK are no fun ), i\'m trying to get the new 1.4 beta running. i\'ve finally gotten all the different packages and stuff i need for the output of \"./configure --without-arts --disable-debug\" to look like this: ========================== === amaroK - WARNING ======================================================== ========================== = = The Ruby programming language is not installed. This means that the lyrics = download feature will not work. Please obtain Ruby (version 1.8 or later) = from http://ruby-lang.org, or install a distribution package. You may install = Ruby at a later time, when amaroK is already installed. = ========================== === amaroK - PLUGINS ======================================================== ========================== = = The following extra functionality will NOT be included: = - aRts-engine = - aKode-engine = - xine-engine = - NMM-engine = - MAS-engine = - Helix-engine = - libvisual Support = - XMMS Visualization Wrapper = - MySql Support = - Postgresql Support = - Konqueror Sidebar = - MusicBrainz Support = - MP4/AAC Tag Write Support = - Moodbar Support = - iRiver iFP Support = = The following extra functionality will be included: = + GStreamer-engine = + iPod Support (with Artwork) = =============================================================================== Good - your configure finished. Start make now so, this seems fine. now, when i run \"make\", i get this at the very end: ../../amarok/src/.libs/libamarok.so: undefined reference to `TagLib::FileRef::addFileTypeResolver(TagLib::FileRef::FileTypeResolver const*)\' collect2: ld returned 1 exit status make[4]: *** [amarokapp] Error 1 make[4]: Leaving directory `/home/adrian/amarok-1.4-beta1/amarok/src\' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/adrian/amarok-1.4-beta1/amarok/src\' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/adrian/amarok-1.4-beta1/amarok\' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/adrian/amarok-1.4-beta1\' make: *** [all] Error 2 it looks like a Taglib error. while this may be, i\'m not sure why as i downloaded the latest version (1.4) and did the ol\' \"./configure, make, make install\" trick without any hassles. so does the amaroK forums collective brain have any suggestions? |
KDE Developer
|
Problem is that you also got an old taglib 1.3 around. You need to get rid of that.
--
Mark Kretschmann - Amarok Developer |
|
hey thanks!
i opened synaptic and completely removed the old 1.3.1 Taglib i had, and now i get a different error ( but at least it\'s a step in the right direction ) : libtool: link: cannot find the library `/usr/lib/libtag.la\' make[4]: *** [amarokapp] Error 1 make[4]: Leaving directory `/home/adrian/amarok-1.4-beta1/amarok/src\' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/adrian/amarok-1.4-beta1/amarok/src\' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/adrian/amarok-1.4-beta1/amarok\' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/adrian/amarok-1.4-beta1\' make: *** [all] Error 2 do i have to add a parameter or something to point make to the location of this libtag.la file? i did a search and i\'ve got one copy in /usr/local/lib and one in the home directory i\'ve got the source code. thanks. (and i really appreciate the prompt reply!!) |
KDE Developer
|
you have to do
./configure --prefix=/usr on taglib, your files aren\'t in place
Annoyed with bbcode since 1999.
|
|
great! that worked well, and amaroK is building my collection as we speak! :cheer:
thanks a lot for all the help. i\'m still realtively new to linux, and although i find myself tearing my hair out a lot, it\'s still fun! i haven\'t felt this way since tinkering on my parent\'s first computer 13 years ago. i kept messing around with the autoexec.bat and config.sys files and then not being able to fix it again afterwards! :lol: anyway, in regards to the \'prefix\' thing in configure, can someone suggest a good resource for learning about that kind of thing? whilst it makes (some) sense to me now, there\'s no way i would\'ve thought to do that myself. it\'d be nice to read something online and feel that penny drop |
KDE Developer
|
hm, haven\'t got a website, maybe just ask google
but the prefix thing is a real basic: if you don\'t tell configure where to place the stuff so --prefix=/usr in most case, it will put it in /usr/local
Annoyed with bbcode since 1999.
|
Registered Member
|
FYI: Doing a
./configure --help already tells a lot of interesting stuff. To give you a direction, ./configure is the output of the autotools (hard to google for it otherwise). There\'s also a file called INSTALL in the source distribution which gives generic build instructions. But as apachelogger already said, --prefix is a basic thing you learn once about and will use it all the time from - and for the rest you run --help, as parameters vary from application to application. |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot], Yahoo [Bot]