viking60 wrote:Well amarok1 is in aur, amarokfs is in aur (You will need yaourt for that). musicmood is in aur as is pacpl-amarok I told you to install yaourt:)
After you have installed it you just do aand amarok1 will be no 14 in the list.Code: Select all
yaourt amarok
Pick it, and do the obvious "Y" and "N" stuff.
______________
And my freezebug behaves a lot like this:
http://bugs.archlinux.org/index.php?do= ... k_id=18944
http://bbs.archlinux.org/viewtopic.php?id=88307
It is driving me mad
Code: Select all
==> Downloading amarok1 PKGBUILD from AUR...
bsdtar: Removing leading '/' from member names
x libmtp.patch
x ruby19_rstring.patch
x gcc45.patch
x amarok-1.4.10.coverfetcher.diff
x PKGBUILD
x gcc44.patch
x amarok_addaspodcast.desktop
x amarok.install
x wikipedia.patch
x ruby19_configure2.patch
Comment by: juanmah on Thu, 03 Jun 2010 15:56:33 +0000
Applying these patches produces later ruby errors, and amarok doesn't compile.
Comment by: ssri on Thu, 03 Jun 2010 22:33:39 +0000
@juanmah: Thanks for trying. Yeah, I applied them as well and met the same luck. I did not know if it was problem on my end.
Comment by: piojo on Sat, 05 Jun 2010 10:48:35 +0000
I get the following error when trying to build this package.
/usr/bin/ld: /usr/lib/../lib64/libstdc++.a(bitmap_allocator.o): relocation R_X86_64_32 against `__gnu_cxx::free_list::_M_get_free_list()::_S_free_list' can not be used when making a shared object; recompile with -fPIC
/usr/lib/../lib64/libstdc++.a(bitmap_allocator.o): could not read symbols: Bad value
I'm on a 64-bit system, and /usr/lib64/libstdc++.so definitely exists. Building amarok with -fPIC doesn't help. Does anyone have any suggestions?
Comment by: juanmah on Mon, 07 Jun 2010 08:48:28 +0000
I rebuild it in x86_64 and it does correctly.
Have you latest gcc?
/usr/lib/libstdc++.a is owned by gcc 4.5.0-4
There isn't no lib64 directory in /usr/lib, neither /usr/lib64.
Comment by: piojo on Wed, 09 Jun 2010 14:22:25 +0000
@juanmah: thank you--I guess my system or libraries are broken. Perhaps it's time for my yearly reinstall :(
Comment by: piojo on Mon, 14 Jun 2010 18:22:45 +0000
I found the cause of my compilation problem. I had a file installed: /usr/lib64/libstdc++.a, which I had assumed was owned by gcc, but it was actually part of llvm-gcc. The amarok build was finding that file and trying to link to it--removing llvm-gcc made the build successful.
First Submitted: Mon, 20 Apr 2009 08:38:35 +0000
amarok1 1.4.10-9 : amaroK - a media player for KDE - v1.4.10 xine engine with wikipedia patch (single package)
( Unsupported package: Potentially dangerous ! )
==> Edit PKGBUILD ? [Y/n] ("A" to abort)
==>And I say... ?
Thanks.
Welcome - good job