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: Thu, 26 Mar 2015 13:35:49 +0100 [thread overview]
Message-ID: <87619oey1m.fsf@gnu.org> (raw)
In-Reply-To: <CACAVtXH9P7SBFPPPYQaHNQWkTPOx1Zb-V7gxVjY4L1oykbGfPw@mail.gmail.com> ("Alexandre \=\?utf-8\?B\?SMOpYXVtw6kiJ3M\=\?\= message of "Wed, 25 Mar 2015 23:22:21 +0100")
Alexandre Héaumé <aheaume@gmail.com> skribis:
> On Wed, Mar 25, 2015 at 9:42 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>
>> 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.
>
> As far as I remember, ./configure passed. Everything I tried so far
> worked except "import pypi".
>
> I can't find a way to make it work with "--with-libgcrypt-prefix".
> On the host, libgcrypt is at "/usr/lib/i386-linux-gnu/libgcrypt.so"
> according to locate, running
>
> ./configure --with-libgcrypt-prefix='/usr/lib/i386-linux-gnu'
Rather:
./configure --with-libgcrypt-libdir='/usr/lib/i386-linux-gnu'
> As it been tried on ubuntu before, and is it worth fixing? I was
> planning on using a spare machine to install GuixSD anyway, it might
> not be worth the effort if compiling and using guix on ubuntu is a
> weird thing to do.
Many people on this list use Guix on top of a Debian derivative or
similar, so no, it’s not a weird thing to do.
HTH,
Ludo’.
next prev parent reply other threads:[~2015-03-26 12:35 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
2015-03-25 22:22 ` Alexandre Héaumé
2015-03-26 12:35 ` Ludovic Courtès [this message]
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=87619oey1m.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).