I recently bought scanner, the driver to which is currently in process and is not yet committed into the main repo, so I downloaded the new code and compiled it into /usr/local/ and openSUSE’s YaST scanner configurer doesn’t see the new versions and continues to work with the old ones. How can I change that? Thanks in advance.
You should explain much, much more about what you did. You seem to think that many of us by reading your two lines of description get the full movie of what you did before their eyes, including things like: what did you download, what statements (exact and precise) did you execute then to make/compile, what statements to install to the correct place, etc, etc. … We need facts, not stories.
Did you do the ‘sudo make install’ step?
If you did, what directory contains the new versions? Did it overwrite the old
drivers?
I downloaded the latest SANE sources from csv and the files to substitute from here: http://rapidshare.com/files/452090227/mp150-files.zip
Then I executed these commands:
autoconf
automake
./configure
make
sudo make install
Everything was compiled into /usr/local/lib/sane/ and other local directories. While the old libs remined here: /usr/lib/sane/ and the YaST scanner configurer cannot see the new ones and sees only the old ones. 
Hope, this is enough. Just tell me what should I do to give more info.
On 03/11/2011 02:36 PM, soshial wrote:
>
> lwfinger;2301872 Wrote:
>> Did you do the ‘sudo make install’ step?
>>
>> If you did, what directory contains the new versions? Did it overwrite
>> the old
>> drivers?
>
> I downloaded the latest SANE sources from csv and the files to
> substitute from here:
> http://rapidshare.com/files/452090227/mp150-files.zip
>
> Then I executed these commands:
> autoconf
> automake
> ./configure
> make
> sudo make install
>
> Everything was compiled into /usr/local/lib/sane/ and other local
> directories. While the old libs remined here: /usr/lib/sane/ and the
> YaST scanner configurer cannot see the new ones and sees only the old
> ones.
>
> Hope, this is enough. Just tell me what should I do to give more info.
The system will find the ones in /usr/lib before the ones in /usr/local/lib.
You can either uninstall the old ones (with YaST?) or repeat the build, but this
time use “./configure --prefix=/usr”. Then the install step will overwrite the
old ones.
Thank you very much! That really helped, but not for long
It revealed that it doesn’t see any libusb libraries, while I do have them all.
configure says:
*** Warning: sane-backends will be built without libusb support. There may
*** be valid reasons to do so, e.g. if you don’t use USB scanners or on
*** platforms without libusb support but generally this means that you
*** can’t use USB devices with SANE. The most probable cause is that
*** the libusb header file usb.h is not installed. If you use Linux
*** you may need a package called ‘libusb-dev’, ‘libusb-devel’ or similar.
I have found only 1 another topic with this problem and it does not seem to have been resolved:(
Canon MP540 and libusb
Any ideas how to repare the links to that library and how to make the system see her?
On 03/11/2011 05:36 PM, soshial wrote:
>
> Thank you very much! That really helped, but not for long
> It revealed that it doesn’t see any libusb libraries, while I do have
> them all.
>
> configure says:
> *** Warning: sane-backends will be built without libusb support. There
> may
> *** be valid reasons to do so, e.g. if you don’t use USB scanners or on
> *** platforms without libusb support but generally this means that you
> *** can’t use USB devices with SANE. The most probable cause is that
> *** the libusb header file usb.h is not installed. If you use Linux
> *** you may need a package called ‘libusb-dev’, ‘libusb-devel’ or
> similar.
>
> I have found only 1 another topic with this problem and it does not
> seem to have been resolved:(
> ‘Canon MP540 and libusb’ (http://tinyurl.com/4sbrm4c)
>
> Any ideas how to repare the links to that library and how to make the
> system see her?
You need to see in which directory the configure script expects to find the
libusb components and either make links in that directory, move the files, or
change the script.
On 03/11/2011 09:36 PM, soshial wrote:
> Then I executed these commands:
> autoconf
> automake
> ./configure
> make
> sudo make install
>
> Everything was compiled into /usr/local/lib/sane/ and other local
> directories. While the old libs remined here: /usr/lib/sane/ and the
> YaST scanner configurer cannot see the new ones and sees only the old
> ones.
my question:
why would the commands used cause new files to NOT overwrite the old
files (as i would expect as normal)?
was it because of the autoconf?
or automake? (both of those are steps i usually do not take–were they
prescribed by the tarballs “README” (or similar)
i usually become root with su - and then run make install (instead of
using sudo), would that make a difference?
or, is the problem that this tarball assummed the layout of some other
distro?
something seems kinda fishy to me!
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
i usually become root with su - and then run make install (instead of
using sudo), would that make a difference?
Nope.
The command ./configure --prefix=/usr --enable-libusb_1_0 solved usb problem but still executing “sudo sane-find-scanner -v -v” (This is sane-find-scanner from sane-backends 1.0.23git) doesn’t see any scanner and sudo scanimage says “scanimage: no SANE devices found”. Moreover, the list of supported scanners in YaST has not updated.
Any thoughts besides using su instead of sudo? 
On 2011-03-12 08:42, DenverD wrote:
> my question:
>
> why would the commands used cause new files to NOT overwrite the old
> files (as i would expect as normal)?
No, the normal or default is /usr/local/. You have to change it yourself.
You are to edit the configure details to your liking, or call the script
with the appropriate parameters.
> i usually become root with su - and then run make install (instead of
> using sudo), would that make a difference?
Not on that.
> or, is the problem that this tarball assummed the layout of some other
> distro?
If you downloaded the sources from the devs, it assumes no distro. I have
no idea what is you got from rapidshare - /that/ is nonstandard.
> something seems kinda fishy to me!
Plain standard to me 
By the way, libusb is not found probably because you need to install some
“…-devel.rpm”.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I shall repeat that the command ./configure --prefix=/usr --enable-libusb_1_0 solved usb problem.
But still:
- executing “sudo sane-find-scanner -v -v” (This is sane-find-scanner from sane-backends 1.0.23git) does not see any scanner and
- sudo scanimage says “scanimage: no SANE devices found”.
Moreover, the list of supported scanners in YaST has not updated.
On 2011-03-14 23:36, soshial wrote:
>
> I shall repeat that the command ./configure --prefix=/usr
> --enable-libusb_1_0 solved usb problem.
I have my doubts.
> Moreover, the list of supported scanners in YaST has not updated.
Well, you could ask the SANE packager, in the mailist.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)