Bingo! Should've realized that, same as --sysconfdir, creates sane/ off of it. Duh. Thanks for all of the help, Now another thing I don't have to fire up Windoze to do.
tj m. allan noah wrote: > I think your --libdir statement is to blame. I bet you have two > installs of sane- one in /usr/lib/sane, and the other in > /usr/lib/sane/sane > > Try configure without that argument, it is not required. > > allan > > On Thu, Apr 22, 2010 at 7:33 PM, tj <999alfred at comcast.net> wrote: > >> I downloaded 1.1.20 and did the following for Slackware 13 installation >> ./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib/sane >> make >> sudo make uninstall >> sudo make install >> >> And now >> ~ $ scanimage -L >> device `epson2:libusb:001:002' is a Epson generic flatbed scanner >> >> No more "no scanning device detected" answer, but xsane gives "no devices >> available" window. But, when I start xsane, the scanner does a "reposition" >> of the scanning element. >> >> I run >> scanimage >image.pnm >> >> and it scans. >> >> Any ideas as to why xsane is not finding the scanner now? >> A lock file left over from the previous install? >> >> tj >> >> >> >> -- >> sane-devel mailing list: sane-devel at lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >> Unsubscribe: Send mail with subject "unsubscribe your_password" >> to sane-devel-request at lists.alioth.debian.org >> >> > > > >
