[sane-devel] Build system issues.

[Olaf Meeuwissen]

"m. allan noah" <kitno455 at gmail.com> writes:

> On Sun, Feb 22, 2009 at 2:06 PM, Chris Bagwell <chris at cnpbagwell.com> wrote:
>> m. allan noah wrote:
>>>
>>> it's not just that it leaves the links behind, it actually makes the
>>> links to 1.0.19, even when 1.1.0 is also installed.
>>>
>> Couldn't find any documentation related to what libtool behaviour should be
>> in tihs area.
>>
>> I just now installed sane 1.0.19 tarball into a private directory and then
>> installed current CVS on top of it.  The behaviour I got seems to be the
>> behaviour you want.  In the end, all symlinks were updated and pointed to
>> latest so.  I had the following in ${prefix}/lib and other backends followed
>> same behaviour.
>>
>> libsane.la
>> libsane.so -> libsane.so.1.1.0
>> libsane.so.1 -> libsane.so.1.1.0
>> libsane.so.1.0.19
>> libsane.so.1.1.0
>>
>> Let me know if you continue to see different behaviour and we can continue
>> to debug it.
>
> Well, It seems to do the base dll backend correctly:
>
> /usr/lib/libsane.so -> libsane.so.1.1.0
> /usr/lib/libsane.so.1 -> libsane.so.1.1.0
>
> but all of the individual backends that were in 1.0.19 are still (partly) wrong:
> /usr/lib/sane/libsane-fujitsu.so -> libsane-fujitsu.so.1.1.0
> /usr/lib/sane/libsane-fujitsu.so.1 -> libsane-fujitsu.so.1.0.19

I'd expect all the backends that were built to get installed the same
way.  Their either all wrong or all right.  Would you happen to be
building only selected backends?  What about the timestamps of the
links?  Do those match with the time you ran `make install`?

> So running scanimage still nets you the wrong one.

Only if your ${libdir}/libsane.so is, or points to, the dll backend.
The dll backend only looks for libsane-*.so.$V_MAJOR files, not for
libsane-*.so.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962               Help support software freedom
                 http://www.fsf.org/jf?referrer=1962