Good advice - I returned scsi-commands to the way I found it and ran the DevSDK.pkg to see if it would fix it and indeed it did, so maybe it fixed other problems as well since I've been having trouble getting KDE 3.2 to complile. I don't actually have a SCSI scanner - I'm just installing this to meet a KDE 3.2 dependency - but thank you for the offer.
William > William Kolean wrote: > >> Thank you Peter and Martin for getting back to me so quickly. On my system, >> scsi-commands wasn't a symbolic link, but I fixed that based on what you >> told me and the compile is now going much better, although it hasn't >> finished yet. >> >> William > > Hi William, > Though it may work for same-backends, you may find later that you have other > things missing that should have been installed by DevSDK.pkg. I'd advise you > to reinstall it anyway. > > On another note, I hope you don't have a scsi scanner... the version of > sane-backends in fink has slightly (okay, completely) broken scsi support. > It will be fixed in the next sane-backends release. If you are too impatient > to wait, let me know and I'll try you with an info file for a sane cvs > snapshot. > > Thanks, > Peter ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
