[sane-devel] Build system issues.

[Chris Bagwell]

m. allan noah wrote:
> Actually chris asked for this previously, but it looks correct:
>
>  /bin/sh ../libtool   --mode=install /usr/bin/install -c
> 'libsane-fujitsu.la' '/usr/lib/sane/libsane-fujitsu.la'
> /usr/bin/install -c .libs/libsane-fujitsu.so.1.1.0
> /usr/lib/sane/libsane-fujitsu.so.1.1.0
> (cd /usr/lib/sane && { ln -s -f libsane-fujitsu.so.1.1.0
> libsane-fujitsu.so.1 || { rm -f libsane-fujitsu.so.1 && ln -s
> libsane-fujitsu.so.1.1.0 libsane-fujitsu.so.1; }; })
> (cd /usr/lib/sane && { ln -s -f libsane-fujitsu.so.1.1.0
> libsane-fujitsu.so || { rm -f libsane-fujitsu.so && ln -s
> libsane-fujitsu.so.1.1.0 libsane-fujitsu.so; }; })
> /usr/bin/install -c .libs/libsane-fujitsu.lai /usr/lib/sane/libsane-fujitsu.la
> PATH="$PATH:/sbin" ldconfig -n /usr/lib/sane
>
> Now here's the crazy thing, if i go and run those commands directly,
> they work properly, and both links are updated.
>
> allan
>   

And just to be sure; did you also run the "ldconfig -n /usr/lib/sane" 
step to verify its not ldconfig doing the wrong thing?

I'm trying to find out more how it works but man page mentions looking 
at "header and filenames" to know which versions should have their 
symlinks updated.  Not sure what header their talking about and if we 
have something mislabelled in it. 

Since we are playing the libtool games with soname as "libsane" instead 
of "libsane-fujitsu", I could envision some tools getting confused by 
that.  But I'm not up to speed yet on how that works.

Chris