Olaf Meeuwissen wrote:
> "m. allan noah" <kitno455 at gmail.com> writes:
>
>
>
>> 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,
>
Hmm, I'll have to look into this concept. Looks like we've always been
calling libtool with the --finish option at the end (1.0.19 anyways)
which will call ldconfig on $(prefix)/lib/sane.
It is probably what we want but it will be a change.
Also, now we are relying on automake's lib install rules which is hard
for me to change its behavior. Whats strange is searching in the
auto-generated backend/Makefile, I can't find any references to "finish"
so I'm not sure how its being invoked right now; but obviously it is.
Chris
