Re: Extension search path changed in 1.9

[Ludovic Courtès]

Hi Andy,

Andy Wingo <address@hidden> writes:

> On Tue 23 Nov 2010 21:56, address@hidden (Ludovic Courtès) writes:
>
>> In 1.8, to run the test suite of libguile-foo from its build tree, I
>> typically had a ‘pre-inst-guile’ like this:
>>
>> exec @abs_top_builddir@/libtool --mode=execute                       \
>>        -dlopen "@abs_top_builddir@/src/libguile-foo.la"      \
>>        @GUILE@ "$@"
>>
>> which amounts to “LD_LIBRARY_PATH=$PWD/src/.libs:$LD_LIBRARY_PATH” on
>> GNU/Linux.
>>
>> However, this no longer works with 2.0: if libguile-foo.so is already
>> present in SCM_EXTENSIONS_DIR, then it will be loaded instead of the one
>> from the build tree.
>
> This sounds like a bad change.  Should we append to the
> LTDL_LIBRARY_PATH environment variable instead?

Yes, let’s do that.  Sounds hackish but it would work.

> I guess that's what we need to do with the libtools that are "out
> there".

The libtool invocations you mean?

Thanks,
Ludo’.