[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libgcrypt
From: |
Ludovic Courtès |
Subject: |
Re: libgcrypt |
Date: |
Thu, 07 Feb 2013 12:08:15 +0100 |
User-agent: |
Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.2 (gnu/linux) |
Andreas Enge <address@hidden> skribis:
> Am Mittwoch, 6. Februar 2013 schrieb Ludovic Courtès:
[...]
>> Passing --with-libgcrypt-prefix allows it to work with non-standard
>> prefixes.
>
> ... under guix, $HOME/.guix-profile/{lib,...} is the standard prefix ;-)
Yes, but it remains “non-standard” to ld.so, ld, etc.
> So would it be possible to modify the test so that it takes LIBRARY_PATH
> into account? (If it were C, the AC macros would do that automatically.) Or
> could one simply use AC_CHECK_LIB?
No, because we precisely want to check that Guile’s ‘dynamic-link’ finds
it, because that’s what is used in guix/utils.scm (in turn,
‘dynamic-link’ uses lt_dlopenext, which uses dlopen.)
Thus the influential environment variables are LTDL_LIBRARY_PATH and
LD_LIBRARY_PATH.
When we have a full-blown distro, all those *PATH variables will be
initialized by /etc/profile, so that everything is transparent. In the
meantime, one has to set them in their own ~/.bashrc.
> If not, a possible work-around would be to check explicitly with the
> $HOME/.guix-profile/lib prefix.
I’d rather let users do one of the above than add something specific.
Ludo’.