Re: [sane-devel] sane-backend 1.0.27 USB broken on Mac with Homebrew

2017-08-07 Thread schmo-fu
Okay, here i go again ... i can confirm, that it is not a permission problem. It's just that there are no files, where they should be. The scanner is recognized by sane-find-scanner now. But scanimage -L doesn't find it, because the sane-backends .conf files are supposed to be at:

Re: [sane-devel] sane-backend 1.0.27 USB broken on Mac with Homebrew

2017-07-28 Thread schmo-fu
gs and Gruß, Thomas.S (aka schmo-fu) Am 28.07.17 um 20:31 schrieb Yurii Kolesnykov: > I had create a PR in homebrew: > https://github.com/Homebrew/homebrew-core/pull/16170 > > Thomas, Tom, please try to install formula from my branch by running: > > brew reinstall > https://ra

Re: [sane-devel] sane-backend 1.0.27 USB broken on Mac with Homebrew

2017-07-27 Thread schmo-fu
but anyway: you use "sane-find-scanner -v" and "scanimage -L". Gruß, Thomas.S (aka schmo-fu) Am 27.07.17 um 21:02 schrieb Tom Myers: > I have a 1XL I can test with with if there is a 1.0.27 built for > macintosh. Just yell where I can download it. >

Re: [sane-devel] sane-backend 1.0.27 USB broken on Mac with Homebrew

2017-07-27 Thread schmo-fu
ps://gist.github.com/6875017d99847cd4bfa5613f61216306 Gruß, Thomas.S (aka schmo-fu) Am 27.07.17 um 14:51 schrieb Yurii Kolesnykov: > Hi, Olaf, Thomas! > > Having another round through the info in the various links you and Yurii >> provided I noticed >> >> checking for pkg-config... no &g

Re: [sane-devel] sane-backend 1.0.27 USB broken on Mac with Homebrew

2017-07-25 Thread schmo-fu
Hi Olaf, sorry for the long wait, but now i'm back at the machine with the scanner. Am 24.07.17 um 14:09 schrieb Olaf Meeuwissen: > > Try --with-usb=yes. That really *should* bomb. > I put '--with-usb=yes' into the formula, but that didn't stop the compilation. You find the log here:

[sane-devel] sane-backend 1.0.27 USB broken on Mac with Homebrew

2017-07-24 Thread schmo-fu
er this is related to the usb-problem is beyond me.) Finally i can say that homebrew-commit 7aaf1e3a14b75a715eed34f3bb4c57e79f417e96 works, while the next commit 60b1305361d0ef61405014b37164b1daaf77d207 doesn't. I hope all of this makes sense to you and someone has time to look into this problem.