libgcrypt

libgcrypt

[Andreas Enge]

[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]

Hello,

I am now trying to configure and build guix with the packages built by 
guix. So I installed autoconf, automake, binutils, glibc, gcc and ld-
wrapper; added
   export GUIX_LD_WRAPPER_ALLOW_IMPURITIES=yes
to my .bashrc as well as PATH, LIBRARY_PATH, CPATH, MANPATH and 
PKG_CONFIG_PATH.

As discussed before, I also added
   export ACLOCAL="aclocal -I $HOME/.guix-profile/share/aclocal" .

Now configure gives the error:
checking for libgcrypt shared library name... libgcrypt
checking for guile... (cached) /home/privat/.guix-profile/bin/guile
checking for guile-config... /home/privat/.guix-profile/bin/guile-config
checking for guile-tools... /home/privat/.guix-profile/bin/guile-tools
checking whether libgcrypt can be dynamically loaded... no
configure: error: GNU libgcrypt does not appear to be usable; see `--with-
libgcrypt-prefix' and `README'.

The file config.log ends with the following lines:
configure:7038: checking for libgcrypt shared library name
configure:7040: result: libgcrypt
configure:7047: checking for guile
configure:7077: result: /home/privat/.guix-profile/bin/guile
configure:7091: checking for guile-config
configure:7109: found /home/privat/.guix-profile/bin/guile-config
configure:7121: result: /home/privat/.guix-profile/bin/guile-config
configure:7135: checking for guile-tools
configure:7153: found /home/privat/.guix-profile/bin/guile-tools
configure:7165: result: /home/privat/.guix-profile/bin/guile-tools
configure:7175: checking whether libgcrypt can be dynamically loaded
configure:7190: result: no
configure:7194: error: GNU libgcrypt does not appear to be usable; see `--
with-libgcrypt-prefix' and `README'.

Do you see why and how to solve it?

Andreas

[-- Attachment #2: Type: text/html, Size: 7214 bytes --]

Re: libgcrypt

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> checking whether libgcrypt can be dynamically loaded... no
> configure: error: GNU libgcrypt does not appear to be usable; see `--with-
> libgcrypt-prefix' and `README'.

Just pass --with-libgcrypt-prefix=$HOME/.guix-profile/lib.

The code corresponding to the check above is simple-minded (it’s in
m4/guix.m4).  All it does is:

  guile -c "(dynamic-func \"gcry_md_hash_buffer\" (dynamic-link \"$LIBGCRYPT\"))"

and checks its return code.

Passing --with-libgcrypt-prefix allows it to work with non-standard
prefixes.

Perhaps README should be augmented?

Ludo’.

Re: libgcrypt

[Andreas Enge]

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

Am Mittwoch, 6. Februar 2013 schrieb Ludovic Courtès:
> Andreas Enge <andreas@enge.fr> skribis:
> > checking whether libgcrypt can be dynamically loaded... no
> > configure: error: GNU libgcrypt does not appear to be usable; see
> > `--with- libgcrypt-prefix' and `README'.
> Just pass --with-libgcrypt-prefix=$HOME/.guix-profile/lib.

Yes, that should work, but...

> The code corresponding to the check above is simple-minded (it’s in
> m4/guix.m4).  All it does is:
>   guile -c "(dynamic-func \"gcry_md_hash_buffer\" (dynamic-link
> \"$LIBGCRYPT\"))"
> and checks its return code.
> Passing --with-libgcrypt-prefix allows it to work with non-standard
> prefixes.

... under guix, $HOME/.guix-profile/{lib,...} is the standard prefix ;-)

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?

If not, a possible work-around would be to check explicitly with the 
$HOME/.guix-profile/lib prefix.

Andreas

[-- Attachment #2: Type: text/html, Size: 5101 bytes --]

Re: libgcrypt

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> 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’.