Re: [gentoo-amd64] Amarok update failure
2009/6/12 Paul Stear gen...@appjaws.plus.com Hello all, I have the following error when updating amarok to version amarok-1.4.10_p20090130-r2 Making all in konquisidebar grep: /usr/lib64/libpcreposix.la: No such file or directory /bin/sed: can't read /usr/lib64/libpcreposix.la: No such file or directory libtool: link: `/usr/lib64/libpcreposix.la' is not a valid libtool archive make[4]: *** [konqsidebar_universalamarok.la] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 * * ERROR: media-sound/amarok-1.4.10_p20090130-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 4357: Called kde_src_compile * environment, line 3143: Called kde_src_compile 'all' * environment, line 3158: Called kde_src_compile 'make' * environment, line 3150: Called die * The specific snippet of code: * emake || die died running emake, $FUNCNAME:make * The die message: * died running emake, kde_src_compile:make Where do I get libpcreposix.la from? I am running KDE 3.5.10 it should belong to libpcre package. i think that you've upgraded that package recently, but you haven't run revdep-rebuild. There re some packages depending on it, and i think that a dependency of amarok is broken after the .la removal. the old kde3.5 version were linking against .la instead of direct lib linking if i recall corectly, and so if a .la file is removed you should rebuild the stuff linked against it. you might also encounter issues rebuilding the broken packages. i still have some 3.5 packages that fail on rebuild, but nowadays i don't really have time to fix them up. anyway, my advice is to run revdep-rebuild and the retry installing amarok. -- dott. ing. beso
Re: [gentoo-amd64] Amarok update failure
On Friday 12 June 2009 10:51:41 Beso wrote: 2009/6/12 Paul Stear gen...@appjaws.plus.com Hello all, I have the following error when updating amarok to version amarok-1.4.10_p20090130-r2 snip Where do I get libpcreposix.la from? I am running KDE 3.5.10 it should belong to libpcre package. i think that you've upgraded that package recently, but you haven't run revdep-rebuild. There re some packages depending on it, and i think that a dependency of amarok is broken after the .la removal. the old kde3.5 version were linking against .la instead of direct lib linking if i recall corectly, and so if a .la file is removed you should rebuild the stuff linked against it. you might also encounter issues rebuilding the broken packages. i still have some 3.5 packages that fail on rebuild, but nowadays i don't really have time to fix them up. anyway, my advice is to run revdep-rebuild and the retry installing amarok. Thanks Beso, I should have thought of that, I am now updating 33 packages so hopefully amarok will install correctly after they have finished. Paul -- This message has been sent using kmail with gentoo linux
Re: [gentoo-amd64] Amarok update failure
Paul Stear wrote: I should have thought of that, I am now updating 33 packages so hopefully amarok will install correctly after they have finished. Paul I'm attempting the lafilefixer solution listed in the libpcre install notes. However, I'm beginning to think I'd have been better off rebuilding 33 packages. I suspect that lafilefixer will work just fine and very quickly solve my problem, but now every time I update just about anything else on my system that produces a .la file I'll get a collision error as just about every .la file is going to have a non-matching mtime and md5sum from its original install...
Re: [gentoo-amd64] Amarok update failure
2009/6/12 Richard Freeman ri...@gentoo.org Paul Stear wrote: I should have thought of that, I am now updating 33 packages so hopefully amarok will install correctly after they have finished. Paul I'm attempting the lafilefixer solution listed in the libpcre install notes. However, I'm beginning to think I'd have been better off rebuilding 33 packages. I suspect that lafilefixer will work just fine and very quickly solve my problem, but now every time I update just about anything else on my system that produces a .la file I'll get a collision error as just about every .la file is going to have a non-matching mtime and md5sum from its original install... always use revdep-rebuild and --as-needed ldflag! this will reduce the rebuild to just the broken packages. -- dott. ing. beso
