On Fri, 26 Jul 2019 02:20:01 +0200 Christopher Gregory via blfs-support <[email protected]> wrote:
>> Sent: Friday, July 26, 2019 at 7:14 AM >> From: "Stephen Berman via blfs-support" >> <[email protected]> >> To: "Ken Moffat via blfs-support" <[email protected]> >> Cc: "Stephen Berman" <[email protected]> >> Subject: [blfs-support] scanimage crashes with hplip plug-in (was: [BLFS >> 8.4] PyQt4 build failure) [...] >> I've retitled this thread, since the original title is no longer the >> problem. Is there anyone here who has built hplip in BLFS, installed >> the scanner plug-in and can use scanimage and xsane? >> >> Steve Berman >> -- >> http://lists.linuxfromscratch.org/listinfo/blfs-support >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page >> > > Hello, > > I hate to be the one who says this, but as you have probably already realized > by now, there is not going to be much that people on this list are going to be > able to suggest to correct this, as it is most likely going to end up being an > issue with the binary. Yes, that seems likely. Still, HP all-in-one devices are pretty common, so I would think that there are other BLFS users with one and it could be helpful to know if some of them are able to use the hplip scanner plug-in under BLFS (while recognizing that may not help me to use it with my device, precisely because it's a binary). > I did read that the configure line and make have to be run as a normal user, > so make sure that you are not running either of these as root. Only the make > install is to be done as root. I did that. > I do not know if the plugin itself is a pre-compiled closed source binary that > gets downloaded and put in place by scripts or not, but if that is the case, > bear in mind that many of the distro's have a 32 bit and a 64 bit version. > You need to make sure that it is a version that has been compiled for your > particular hardware. For the rest of hplip there was no issue around the architecture, so I assume the binary plugin also handles that. Mostly hplip consists of Python scripts, and though my Python foo is quite limited, AFAICT all the grunt work of the plugin installation is done within the binary itself, so there's no way I can see to check it or experiment with it. > Also check that the installation has not done something > unexpected by placing one or more files in either the /usr/local location, or > in /usr/lib64. It does indeed install files under both /usr/local/lib and /usr/lib64, but symlinks these to /usr/lib. I also compared the files installed in BLFS with what's in openSUSE Tumbleweed and see no significant differences. > These are the only suggestions that I can think of. I appreciate them. > Once you have double checked all these, if it is indeed a closed binary, it > would be time to locate their current bug tracker and post a bug report. It > may be that on lfs/blfs that a newer version of a package has had a change > made in it that is causing the issue. Yes, that's probably the next step I'll take. > Regards, > > Christopher. Thanks, Steve Berman -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
