On Tue, Nov 07, 2006 at 08:24:33AM +0900, Olaf Meeuwissen wrote: > [email protected] writes: > > > On Mon, Nov 06, 2006 at 09:19:38AM +0000, [email protected] wrote: > >> On Sat, Nov 04, 2006 at 07:12:39PM -0500, m. allan noah wrote: > >> > On Sat, 4 Nov 2006 [email protected] wrote: > > [snip] > >> > > > >> > >If I run "scanimage -L" as root it says "No scanners were identified". > >> > > > >> > >If I run "xsane" or "xscanimage" as root they find both my scanners. > >> > > >> > the fact that scanimage does not work, but xsane does, generally means > >> > that you have two copies of sane-backends installed, often the distro's > >> > original one, and one in /usr/local > >> > > >> Ah, thanks, it's possible that I do have two copies of sane installed, > >> I'll investigate. > >> > > It's not that I have two copies of sane installed, it's the various > > "add-ons" that have screwed things up. It would appear that both the > > HPLIP/CUPS installation and the iscan installation have assumed a base > > directory of /usr/local whereas the basic sane installation is in > > /usr. > > The iscan RPMs use /usr (and are not relocatable). If you compiled > from source, the ./configure script is GNU standards compliant and > uses /usr/local as the default prefix. A look at: > > $ ./configure --help > > would have told you that. You can easily recompile for /usr with > > # ./configure --prefix=/usr > Yes, that's exactly what I have done (after uninstalling the /usr/local version of iscan) and, as I have already reported here, it has fixed all of my problems.
It's just unfortunate that my Slackware package install of sane put it in /usr and the iscan install went to /usr/local by default. Normally one *can* install 'non standard' packages (i.e. stuff that's not part of the Slackware distribution) in /usr/local without problems. Iscan is an exception and needs to be in the same place as the rest of sane. -- Chris Green ([email protected])
