Andy Wingo writes:
> On Fri 11 Feb 2011 17:01, l...@gnu.org (Ludovic Courtès) writes:
>
>>> I guess that's what we need to do with the libtools that are "out
>>> there".
>>
>> The libtool invocations you mean?
>
> No, the libltdls. I was thinking about getting some other API into
> ltdl, instead
On Fri 11 Feb 2011 17:01, l...@gnu.org (Ludovic Courtès) writes:
>> I guess that's what we need to do with the libtools that are "out
>> there".
>
> The libtool invocations you mean?
No, the libltdls. I was thinking about getting some other API into
ltdl, instead of hacking at environment variab
Hi Andy,
Andy Wingo writes:
> On Tue 23 Nov 2010 21:56, l...@gnu.org (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 \
>>
Hi Ludovic,
On Tue 23 Nov 2010 21:56, l...@gnu.org (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_
Hello!
‘sysdep_dynl_init’ has been doing this for some time in 1.9:
--8<---cut here---start->8---
env = getenv ("GUILE_SYSTEM_EXTENSIONS_PATH");
[...]
if (env)
lt_dladdsearchdir (env);
else
{
lt_dladdsearchdir (SCM_LIB_DIR);
lt_dla
