From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: `--run=simple` error ?
Date: Fri, 22 Feb 2019 17:22:39 +0100 [thread overview]
Message-ID: <CAJ3okZ2-yi+kGXL76vkZbCM34oswcg3KGS4pD_MFQkTPguVNJA@mail.gmail.com> (raw)
In-Reply-To: <87pnrl40j8.fsf@elephly.net>
Hi Ricardo,
Thank you for your help.
On Thu, 21 Feb 2019 at 16:40, Ricardo Wurmus <rekado@elephly.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
> I think you should unset GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH as
> you’re working in an environment anyway.
Ok.
I have unset and also tried with --pure and --container.
No effect.
> … 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.
So, I removed the Guix modules installed (e.g. with guix environment
gwl) and then I reinstalled them. Now, it seems to work. \o/
Well, if I understand well, because I am running Guix on a foreign
distro, there is a "big dance" with the Guix modules. Somehow, it is
similar with one emacs-guix issue on non full GuixSystem explained in
the second part of this message [1].
You proposed something here [2] but to be honest I have not tried yet
because my mind is not clear about all that.
If it is the similar issue than the emacs-guix one, we need to propose
or document the issue because it is tricky.
[1] https://lists.gnu.org/archive/html/help-guix/2019-01/msg00020.html
[2] https://lists.gnu.org/archive/html/help-guix/2019-01/msg00041.html
Well, now I can play again with the GWL. ;-)
Thank you again.
All the best,
simon
next prev parent reply other threads:[~2019-02-22 16:23 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 [this message]
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
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=CAJ3okZ2-yi+kGXL76vkZbCM34oswcg3KGS4pD_MFQkTPguVNJA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
/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).