[sane-devel] problem installing sane-backends: invalid libtool wrapper script scanimage

Henning Meier-Geinitz henning@meier-geinitz.de
Tue, 11 May 2004 22:36:23 +0200


On Tue, May 11, 2004 at 01:39:14AM +0200, Antoine Jacoutot wrote:
> I'm having a problem installing sane-backends from source on OpenBSD; it 
> compiles fine (./configure && make) but when doing make install, it stops 
> after a while with the following error:

I haven't tested sane on OpenBSD for quite some time. I remeber some
trouble with dynamic loading that time but compilation worked (1.0.12
I think).

> gmake[1]: Entering directory 
> `/usr/ports/local/sane-backends/w-sane-backends-1.0.14/sane-backends-1.0.14/frontend'
> ../mkinstalldirs /usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/local/bin /usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/local/sbin /usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/local/share
> mkdir /usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/local/bin
> mkdir /usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/ports/local/sane-backends/w-sane-backends-1.0.14/fake-i386/usr/local/sbin
> libtool: install: invalid libtool wrapper script `scanimage'
> gmake[1]: *** [install] Error 1
> gmake[1]: Leaving directory 
> `/usr/ports/local/sane-backends/w-sane-backends-1.0.14/sane-backends-1.0.14/frontend'
> gmake: *** [install-recursive] Error 1
> *** Error code 2
> Stop in /usr/ports/local/sane-backends
> Any idea what this mean ?

The "wrapper script" is a trick of libtool. It's used to be able to
run binaries that use self-compiled libraries without prior
installation of the libraries. So you can run "scanimage" directly
from the sane source directory without installing sane.

That's the theory at least. libtool uses a wrapper script that
replaces the scanimage binary for that prupose. SOmething went wrong
with that script but I have no clue what.