"m. allan noah" <kitno455 at gmail.com> writes:
> On Thu, Feb 26, 2009 at 9:46 PM, Chris Bagwell <chris at cnpbagwell.com>
> wrote:
>> 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?
>
> now i did, and yes- that is the culprit.
One should *not* run ldconfig on the directory holding the backends,
ie ${sanelibdir}. Frontends should link against libsane which is in
${libdir}. If one absolutely insists on running ldconfig it should be
run on ${libdir}.
IIRC, Mandrake (before it became Mandriva) and Turbolinux had bugs in
their %postinst sections that ran ldconfig on ${sanelibdir} and broke
their SANE installations.
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
