First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 41013
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Maciek <MacBerry@mail.ru>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 41013 depends on: 40901 Show dependency tree
Bug 41013 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-02-09 14:00 0000 
Hello,
After emerging libfam 2.7, I noticed that libfam library is now called libfam.0 and not libfam.so.0. That means that kde 3.1 refuses to start (it seeks libfam.so.0).
A simple ln -s libfam.0.0.0 libfam.so.0 resolves the problem.
I checked the forums, it seems I am not the only one to have this problem...



Reproducible: Always
Steps to Reproduce:
1. Emerge fam 2.7.0
2. Try to start kde (or licq, or anything that needs libfam)

Actual Results:  
libfam.so.0 not found


(I am putting this as "major". Sorry if it's to severe...)

------- Comment #1 From Spider (RETIRED) 2004-02-09 15:30:23 0000 ------- 
Great!   Another libtool bug. Just what We Need.

------- Comment #2 From SpanKY 2004-02-09 18:00:21 0000 ------- 
fixed in cvs

------- Comment #3 From Spider (RETIRED) 2004-02-10 15:28:17 0000 ------- 
*** Bug 41078 has been marked as a duplicate of this bug. ***
First Last Prev Next    No search results available      Search page      Enter new bug