From: ludo@gnu.org (Ludovic Courtès)
To: "Alexandre Héaumé" <aheaume@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: import pypi: undefined symbol __gmpn_cnd_sub_n
Date: Wed, 25 Mar 2015 21:42:12 +0100 [thread overview]
Message-ID: <87619okdwb.fsf@gnu.org> (raw)
In-Reply-To: <CACAVtXEbvwpFfBaP==j6j5AHEEv+B8LG1vFeEuabWHc-ecpv_g@mail.gmail.com> ("Alexandre \=\?utf-8\?B\?SMOpYXVtw6kiJ3M\=\?\= message of "Wed, 25 Mar 2015 19:05:20 +0100")
Alexandre Héaumé <aheaume@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> It’s unclear to me how libhogweed.so gets loaded (nothing here depends
>> on Nettle, AFAIK.) But it looks like the problem is that /usr/bin/guile
>> (which comes from the host distro) is trying to dlopen stuff that is
>> built with Guix. This usually won’t work notably because that would try
>> to load different copies of libc.so, libgmp.so, etc.
>
> Makes sense. The guile-gnutls package in ubuntu depends on libhogweed,
> so that's where it comes from.
Oh right, I forgot this one.
> Is it possible that the guile-gnutls bindings from guix are chosen
> over the host bindings, or something along these lines?
Yes, it seems to be the case. When using Guile from the host distro,
you must use guile-gnutls from the host distro as well.
>> If it does, could you run, from Guix’s top-level build tree:
>>
>> ./pre-inst-env guile -c '(use-modules (json) (guix pk-crypto))'
[...]
> ERROR: In procedure dynamic-link:
> ERROR: In procedure dynamic-link: file: "libgcrypt", message: "file not found"
Weird, did ./configure even pass? You can run:
./configure --with-libgcrypt-prefix=/usr/whatever/
to make sure it picks libgcrypt.so from the host distro.
HTH,
Ludo’.
next prev parent reply other threads:[~2015-03-25 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 12:25 import pypi: undefined symbol __gmpn_cnd_sub_n Alexandre Héaumé
2015-03-25 16:41 ` Ludovic Courtès
2015-03-25 18:05 ` Alexandre Héaumé
2015-03-25 20:42 ` Ludovic Courtès [this message]
2015-03-25 22:22 ` Alexandre Héaumé
2015-03-26 12:35 ` Ludovic Courtès
2015-03-27 18:54 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87619okdwb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=aheaume@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).