I am having trouble compiling the development version of SANE now,
unfortunately, straight from the repository.
System:
32-bit Debian unstable
installed version of SANE: 1.0.2
I do the following as root:
cd ~/src
git clone git://git.debian.org/sane/sane-backends.git
cd sane-backends
autoconf
automake
BACKENDS="pixma epson2" ./configure
make
make install
Everything up to and including "make" seems to end perfectly.
Unfortunately, make install fails. Here is the last part of the
output:
...
make install-data-hook
make[4]: Entering directory `/home/gernot/src/sane-CVS/sane-backends/backend'
rm -f /usr/local/lib/sane/libsane.*
test -z "/usr/local/etc/sane.d" || /bin/mkdir -p "/usr/local/etc/sane.d"
test -z "/usr/local/etc/sane.d/dll.d" || /bin/mkdir -p
"/usr/local/etc/sane.d/dll.d"
NOT overwriting pixma.conf in /usr/local/etc/sane.d...
NOT overwriting epson2.conf in /usr/local/etc/sane.d...
NOT overwriting saned.conf in /usr/local/etc/sane.d...
NOT overwriting dll.conf in /usr/local/etc/sane.d...
for dir in artec_eplus48u gt68xx snapscan epjitsu ; do \
/bin/bash ../mkinstalldirs /usr/local/share/sane/${dir} ; \
done
/bin/bash ../mkinstalldirs -m 775 -g uucp /usr/local/var/lock/sane
Usage: mkinstalldirs [-h] [--help] [--version] [-m MODE] DIR ...
Create each directory DIR (with mode MODE, if specified), including all
leading file name components.
Report bugs to <bug-automake at gnu.org>.
make[4]: *** [install-lockpath] Error 1
make[4]: Leaving directory `/home/gernot/src/sane-CVS/sane-backends/backend'
make[3]: *** [install-data-am] Error 2
make[3]: Leaving directory `/home/gernot/src/sane-CVS/sane-backends/backend'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/gernot/src/sane-CVS/sane-backends/backend'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/home/gernot/src/sane-CVS/sane-backends/backend'
make: *** [install-recursive] Error 1
I don't see an explicit reason given (such as permissions missing).
Searching for comments regarding the actual error line yields no
recent results (an error like this apparently existed in 1.0.20 in
2009 for some gentoo users, according to search results).
Any pointers much appreciated.
Regards,
Gernot Hassenpflug
I wonder if there is
