1 |
On Wed, 2016-10-05 at 23:45 +0200, Bertram Scharpf wrote: |
2 |
> Hi, |
3 |
> |
4 |
> my olde Brother printer/scanner device MFC-7420 needs |
5 |
> libraries that are provided as binaries on the Brother site. |
6 |
> Until I switched to amd64 they worked well on a x64 system. |
7 |
> |
8 |
> Now I loaded down the amd64 version but it doesn't work. The |
9 |
> problem seems to be a library load. |
10 |
> |
11 |
> # SANE_DEBUG_DLL=1 scanimage -L |
12 |
> [sanei_debug] Setting debug level of dll to 1. |
13 |
> [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends |
14 |
> 1.0.24 |
15 |
> [dll] load: dlopen() failed (libusb-0.1.so.4: cannot open shared |
16 |
> object file: No such file or directory) |
17 |
> ... |
18 |
> |
19 |
> No scanners were identified. ... |
20 |
> |
21 |
> Indeed, "libusb-0.1.so.4" is hardcoded in |
22 |
> "libsane-brother2.so". The libraries present are |
23 |
> |
24 |
> # equery b /lib64/libusb-* |
25 |
> * Searching for /lib64/libusb-1.0.so.0,/lib64/libusb-1.0.so.0.1.0 |
26 |
> ... |
27 |
> dev-libs/libusb-1.0.19-r1 (/lib64/libusb-1.0.so.0.1.0) |
28 |
> dev-libs/libusb-1.0.19-r1 (/lib64/libusb-1.0.so.0 -> libusb- |
29 |
> 1.0.so.0.1.0) |
30 |
> |
31 |
> When I use brute force and symlink 0.1 to 1.0 I get another |
32 |
> error that doesn't actually surprise me. |
33 |
> |
34 |
> # ln -s libusb-1.0.so.0.1.0 libusb-0.1.so.4 |
35 |
> # SANE_DEBUG_DLL=1 scanimage -L |
36 |
> [sanei_debug] Setting debug level of dll to 1. |
37 |
> [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends |
38 |
> 1.0.24 |
39 |
> [dll] load: dlopen() failed (/usr/lib64/sane/libsane-brother2.so.1: |
40 |
> undefined symbol: usb_busses) |
41 |
> ... |
42 |
> |
43 |
> Brother provides a source package but I cannot compile that |
44 |
> because it isn't even complete, and when I mail them, they |
45 |
> don't answer. |
46 |
> |
47 |
> Is there _any_ way to solve this? |
48 |
> |
49 |
> Thanks in advance. |
50 |
> |
51 |
> Bertram |
52 |
> |
53 |
> |
54 |
|
55 |
I recently started using the brother-overlay[0], and so far the drivers |
56 |
have "just worked" for me. I can't tell offhand if your driver is |
57 |
included there. |
58 |
|
59 |
[0] https://github.com/stefan-langenmaier/brother-overlay |
60 |
|
61 |
Alecks Gates |