<br><br><div class="gmail_quote">On Thu, Feb 26, 2009 at 10:07 PM, m. allan noah <span dir="ltr"><<a href="mailto:kitno455@gmail.com">kitno455@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Thu, Feb 26, 2009 at 11:00 PM, Chris Bagwell <<a href="mailto:chris@cnpbagwell.com">chris@cnpbagwell.com</a>> wrote:<br>
> m. allan noah wrote:<br>
>><br>
>> On Thu, Feb 26, 2009 at 9:46 PM, Chris Bagwell <<a href="mailto:chris@cnpbagwell.com">chris@cnpbagwell.com</a>><br>
>> wrote:<br>
<br>
> Here is an idea to explore... Is there any change your RPM package is<br>
> replacing ltmain.sh or libtool when it was compiled? I could see how<br>
> ldconfig might behavior like your seeing if 1.0.19 backends were installed<br>
> with "soname"'s of the form libsane-backend.so.1 but your 1.1.0 backends<br>
> were installed with soname's of the form libsane.so.1.<br>
><br>
<br>
</div></div>Its not 'my' rpm- it is the distro's rpm, which happens to be: Fedora<br>
10, tada! Now you can test it too :)<br>
<div><div></div><div class="Wj3C7c"></div></div></blockquote><div><br>Yep, that appears to be the issue... at least at first glance. This line is in Fedora 10's spec file:<br><br> # We patched <a href="http://configure.in">configure.in</a>, so regenerate configure.<br>
autoreconf --install --force<br><br>They should remove that --force option so as not to overwrite our patched ltmain.sh. So using Fedora RPM's and then installing on top with source package will have the unwanted behavior you are seeing.<br>
<br>I'll bugzilla that when I have a moment.<br><br>Chris<br></div></div><br>