Thank you a lot for this.
I've just checked everything again, recompiled my code as well (I'm
using SCons so it detects that the headers and the libraries changed)
and it works without a warning.
Matthieu
2009/5/12 Jeff Squyres :
> On May 12, 2009, at 8:17 AM, Matthieu Brucher wrote:
>
>> OK, th
On May 12, 2009, at 8:17 AM, Matthieu Brucher wrote:
OK, this is indeed the case. I'll try to clean the tree (I have
several other package and deleted the original 1.2.8 package) and test
again.
This misleading libltdl error message continues to bite us over and
over again (users and devel
2009/5/12 Jeff Squyres :
> Or it could be that you installed 1.3.2 over 1.2.8 -- some of the 1.2.8
> components that no longer exist in the 1.3 series are still in the
> installation tree, but failed to open properly (unfortunately, libltdl gives
> an incorrect "file not found" error message if it
Or it could be that you installed 1.3.2 over 1.2.8 -- some of the
1.2.8 components that no longer exist in the 1.3 series are still in
the installation tree, but failed to open properly (unfortunately,
libltdl gives an incorrect "file not found" error message if it is
unable to load a plugi
