Re: [sane-devel] Unsupported device: Canon MF4018
Chris Bagwell wrote: > FYI: There was a three day window (around Feb. 17th) that CVS code > wouldn't look for config files in correct location. I think that > explains your need to cd. Current CVS is fixed in this area. > > Also, there was a 1 or 2 week window at beginning of Feb. where CVS set > version number of sane as libsane-0.1.0; which looked "older" then the > libsane-1.0.0 that your distribution would have installed. So in > certain cases, xsane or scanimage may have perfered your truely older > sane-1.0.xx version. > > You may wish to do "ldd /path/to/scanimage" and "ldd /path/to/xsane" to > make sure your not having some rpath issues where its forced to only use > old or wrong sane shared libraries. Nicolas Martin wrote: > Normally, you can install Sane in the /usr/local, as long as lib > directories are correctly set in /etc/ld.so.conf and > in /etc/ld.so.conf.d/* > > In this case, uninstalling first the Sane package coming with your Linux > distribution in /usr/lib is important, as ldconfig checks first /usr/lib > to look for libraries. Otherwise, you can also compile Sane CVS with the > --prefix=/usr --sysconfdir=/etc configure options, so that libs and > binaries will go in /usr/lib and /usr/bin, not messing up with 2 Sane > installations. > > Also, to run scanimage in /usr/local/bin from anywhere, did you check > your $PATH variable, to contain /usr/local/bin ? Thank you for information. I tried ldd, but it didn't help scanimage. There is line '/usr/local/lib' in my /etc/ld.so.conf (and in Slackware there is no /etc/ld.so.conf.d). And the old version of Sane is completely removed. My $PATH variable contains /usr/local/bin (scanimage *runs* from anywhere, but *can't find the scanner* from anywhere). If I have time, I will try a fresh snapshot of Sane and report result to the list. Gleb