[sane-devel] Boeder SmartScan Slim Edition on SuSE

[Henning Meier-Geinitz]

Hi,

On Tue, Feb 10, 2004 at 10:31:48PM -0000, Jim George wrote:
> Now I am confused.  Here is the output from ldd on libsane-gt68xx.so.1.0.13
> 
> tassi:/usr/lib/sane # ldd libsane-gt68xx.so.so.1.0.13
> ldd: ./libsane-gt68xx.so.so.1.0.13: No such file or directory
> tassi:/usr/lib/sane # ldd libsane-gt68xx.so.1.0.13
>         libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0x4002c000)
>         libnsl.so.1 => /lib/libnsl.so.1 (0x40033000)
>         libm.so.6 => /lib/i686/libm.so.6 (0x40049000)
>         libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4006c000)
>         libdl.so.2 => /lib/libdl.so.2 (0x4008a000)
>         libc.so.6 => /lib/i686/libc.so.6 (0x4008d000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> tassi:/usr/lib/sane #
> 
> Both libsane-gt68xx.so.1 and libsane-gt68xx.so are linked to
> libsane-gt68xx.so.1.0.13.

Theoretically it's possible that sane was linked to libusb but has no
libusb support. That may happen if sane was compiled without libusb
first and then libusb was installed and sane was relinked. Running
"make distclean" in this case makes sense ...

Another possible source of that problem: The libsane-gt68xx.so you are
looking at is not the libsane.so that get's loaded when you run
scanimage. Check for other libsane-gt68xx.so.

Setting SANE_DEBUG_DLL=255 will print which lib is used. Example:

[dll] load: searching backend gt68xx' in /usr/local/lib/sane'
[dll] load: trying to load /usr/local/lib/sane/libsane-gt68xx.so.1'
[dll] load: dlopen()ing /usr/local/lib/sane/libsane-gt68xx.so.1'

Bye,
  Henning