unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: `--run=simple` error ?
Date: Fri, 22 Feb 2019 17:35:09 +0100	[thread overview]
Message-ID: <87y3673hoi.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ2-yi+kGXL76vkZbCM34oswcg3KGS4pD_MFQkTPguVNJA@mail.gmail.com>


zimoun <zimon.toutoune@gmail.com> writes:

>> … that’s likely due to ABI change in Guix.  Have you cleared all .go
>> files?  Do you still get this when GUILE_LOAD_COMPILED_PATH and
>> GUILE_LOAD_PATH are unset?
>
> All .go where ?
> In the GWL checkout, yes. It was the first thing I tried. :-)
> Otherwise, no I have not cleared any .go files. Which ones I need to clear?
>
> From my understanding, the issue comes from: GWL compiles with
> /gnu/store/9alic3caqhay3h8mx4iihpmyj6ymqpcx-guile-2.2.4/bin/guile
>
> But GWL needs guix modules and these modules have been compiled with
> another Guile, I guess.
> /gnu/store/r658y3cgpnf99nxjxqgjiaizx20ac4k0-guile-2.2.4/bin/guile
>
> And the ABI issue perhaps comes from that.

No, the version of Guile is not at fault here.  It’s about the version
of Guix.

(The GWL builds with Guix as an input.)

I’m not sure what’s the best way to install the GWL, to be honest.
Should it be a mere channel that extends the *current* Guix?  If it is
built with Guix then it refers to an older version of Guix (namely the
older version that is available through Guix itself), so that’s not
actually desirable.

I think it should work with “guix pull” to stay current and ensure that
it has access to the same packages that a user would see on the command
line.  Currently, this only works through a channel.  I don’t really
like that, though.

--
Ricardo

  parent reply	other threads:[~2019-02-22 16:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 15:22 `--run=simple` error ? zimoun
2019-02-21 15:40 ` Ricardo Wurmus
2019-02-22 16:22   ` zimoun
2019-02-22 16:33     ` Pjotr Prins
2019-02-22 16:48       ` zimoun
2019-02-22 16:57         ` Pjotr Prins
2019-02-22 21:05           ` zimoun
2019-02-22 21:18             ` Pjotr Prins
2019-02-24 11:40               ` zimoun
2019-02-24 12:02                 ` Pjotr Prins
2019-02-22 16:35     ` Ricardo Wurmus [this message]
2019-02-22 16:55       ` zimoun
2019-02-22 17:04         ` Ricardo Wurmus
2019-02-22 21:10           ` zimoun
2019-02-22 22:54             ` Ricardo Wurmus
2019-02-24 11:56               ` zimoun

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://www.guixwl.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3673hoi.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=gwl-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).