From: "Thompson, David" <dthompson2@worcester.edu>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix with guile-next
Date: Fri, 7 Oct 2016 12:31:36 -0400 [thread overview]
Message-ID: <CAJ=RwfZmQEc2O-bgMBd85dXjkCRZBvrkXqW7ydiZbR=qBzquBg@mail.gmail.com> (raw)
In-Reply-To: <CAJ98PDxHBz-5DA4Nvbh4gFG6U=Nxrr8MUvUHXA4usEYZO8t8cQ@mail.gmail.com>
On Fri, Oct 7, 2016 at 12:19 PM, Catonano <catonano@gmail.com> wrote:
> If I do
>
> $ guix environment --ad-hoc guix guile
> $ guile
>> (use-modules (guix http-client))
>
> it's ok.
>
> If I do
>
> $ guix environment --ad-hoc guix guile-next ;; <-- note the "-next"
> $ guile
>> (use-modules (guix http-client))
>
> Then there is no code for module http-client
This is because Guix is built with Guile 2.0, not Guile 2.1. You need
to make a variant of the guix package that uses guile-next.
- Dave
next prev parent reply other threads:[~2016-10-07 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 16:19 guix with guile-next Catonano
2016-10-07 16:31 ` Thompson, David [this message]
2016-10-07 16:47 ` Amirouche Boubekki
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='CAJ=RwfZmQEc2O-bgMBd85dXjkCRZBvrkXqW7ydiZbR=qBzquBg@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=catonano@gmail.com \
--cc=help-guix@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.
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).