David R. Morrison wrote:
OK, in that case, you'll need to go into the build directory and examine both configure and config.log to see what kind of test it is performing for the kdelibs, and how that test failed. Sometimes these things are caused by an implicit dependency on a library which should have been given in the fink package but wasn't...
-- Dave
P.S. No, I've not attempted K3B and don't even know what it is... I am just giving general troubleshooting advice.
For all KDE apps, you'll generally want to do what I'm doing in the KDE packages, and unpack a new admin/ directory over the one that ships with the software, because it is unlikely to work correctly with darwin.
Get the kde-admindir tarball and unpack it (if you've built kde from source in fink, you already have it in /sw/src, otherwise a "fink fetch kdelibs3" should get it), then do "make -f admin/Makefile.common cvs" and then the normal config stuff.
-- Benjamin Reed, a.k.a. RangerRick [EMAIL PROTECTED] / http://ranger.befunk.com/
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
