Bug 62204 - KDevelop requires libfam but does not scan for it during configure step
Summary: KDevelop requires libfam but does not scan for it during configure step
Status: RESOLVED DUPLICATE of bug 61585
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-05 19:58 UTC by Chris Thompson
Modified: 2003-08-05 21:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Thompson 2003-08-05 19:58:37 UTC 
Version:           KDevelop 3.0a5 from cvs (using KDE KDE 3.1)
Installed from:    Mandrake RPMs
OS:          Linux

Compiling KDevelop 3.0a5 from today's cvs failed.  The configure step worked as expected but one of the components required libfam to be already installed.  I would expect if this library is required that it would be scanned for during the configure step rather than having the compile fail.

Once I installed libfam (libfam-dev from Mandrake), the configure and make worked (or at least, got past this point).
Comment 1 Thiago Macieira 2003-08-05 21:35:50 UTC 
Hello, I believe this is a duplicate.  
  
It's not kdevelop that requires libfam. It's one of the libraries that kdevelop links against.  
The bug is inside the Mandrake RPMs for the -devel package that provided that library 
(probably kdelibs-devel). 

*** This bug has been marked as a duplicate of 61585 ***