Summary: | KDELibs Ebuild failed while trying to link libmad | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel <dannonz> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | ferret-bgo, k |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic.php?t=92525&highlight=libmad | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Just libmad.la as a text file |
Description
Daniel
2003-11-26 12:43:04 UTC
Can you eyeball /usr/lib/libmad.la and see if it has a reference to that file? root@leagueworks lib # pwd /usr/lib root@leagueworks lib # ls -l libmad.la -rwxr-xr-x 1 root root 693 Nov 27 09:05 libmad.la Sorry is that hat you mean? :) *relative linux newbie...* Created attachment 21333 [details]
Just libmad.la as a text file
The upload was what I meant, thank you. Unfortunately it doesn't give any clue as to why this is going wrong. I'll see if I can duplicate the problem. Just to let you know, the workaround: ln -s / /var/tmp/portage/libmad-0.15.0b-r1/image allowed me to emerge kdelibs successfully as per the forum post... Hopefully that will give you some idea as to what might be going wrong... You should *not* make that link. Doing so is very bad =p Anyway, my friend who also had this problem had a slightly different situation, as seen from this grep: luke-jr@chewy lib $ grep image libmad* libmad.la:libdir='/var/tmp/portage/libmad-0.15.0b-r1/image//usr/lib' Changing this path to what it should be should fix the problem. I have same problem, however, in libmad.la, line 32: libdir='/usr/lib' . Had this same problem with someone in #gentoo, got them to do luke-jr's grep and got the same result he did. Funnily enough, I then checked it on my system and found I had it too. However, My arts-1.2.0_rc1 compiled just fine (it's a masked version). I'm not sure why. I have USE="mad". Had one person having this problem with /usr/lib/libfreetype.la this stuff has all been fixed, but you may need to perform some manual cleanup as described in the forums. it's a bug elsewhere |