Thanks Gleb for your feedback, I'll update the pixma backend
documentation with this information.
Nicolas
Le lundi 23 f?vrier 2009 ? 13:16 +0300, Gleb Baryshev a ?crit :
m. allan noah wrote:
You have two copies of sane installed?
Before installing sane-2009-02-19, I ran '# removepkg
Normally, you can install Sane in the /usr/local, as long as lib
directories are correctly set in /etc/ld.so.conf and
in /etc/ld.so.conf.d/*
In this case, uninstalling first the Sane package coming with your Linux
distribution in /usr/lib is important, as ldconfig checks first /usr/lib
to look
This lead to some direct exchanges between us a while back, but it looks
to me more like some low level usb issue between the MF4660 scanner and
libusb ?
The scanner stops responding at some point, but all the pixma backend
messages exchanged look identical to those in the Win Snoop.
So don't
hi
Running a make dist on a freshly configured CVS tree bugs out with the
following:
bash-3.2$ make dist
{ test ! -d sane-backends-1.1.0-cvs || { find sane-backends-1.1.0-cvs
-type d ! -perm -200 -exec chmod u+w {} ';' rm -fr
sane-backends-1.1.0-cvs; }; }
test -d sane-backends-1.1.0-cvs || mkdir
is it time to dump japi? comments anyone?
allan
On Sat, Feb 28, 2009 at 11:55 AM, Louis Lagendijk
louis at lagendijk.xs4all.nl wrote:
hi
Running a make dist on a freshly configured CVS tree bugs out with the
following:
bash-3.2$ make dist
{ test ! -d sane-backends-1.1.0-cvs || { find
hi
In order to better keep track of what I installed, I am trying to build
an RPM package for Sane on my Fedora 10 box.
This fails as the config files do not get installed. This seems to be
caused by the install-becfg target in backend/Makefile.am
@list=$(BACKEND_CONFS_ENABLED) saned.conf
--
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090228/d530d0dd/attachment.htm
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090228/2e1511d9/attachment-0001.htm
Technically, there is no failure listed below. It looks as if it
created the tar.gz file just fine. Those are just warning messages from
the java compiler.
But I see now that the way I did the makefiles that
backend/dll-preload.h gets needlessly created during make dist and
that the java
