From: zimoun <zimon.toutoune@gmail.com>
To: "Denis 'GNUtoo' Carikli" <GNUtoo@cyberdimension.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: How to build Guix to send a patch when Guix build fails?
Date: Fri, 2 Oct 2020 10:08:47 +0200 [thread overview]
Message-ID: <CAJ3okZ3nCFvk=XhtA22yUMbQ70+tqZO5Et3d6bOeoZZ2LN2pug@mail.gmail.com> (raw)
In-Reply-To: <20201002011957.48294d32@primarylaptop.localdomain>
On Fri, 2 Oct 2020 at 01:22, Denis 'GNUtoo' Carikli
<GNUtoo@cyberdimension.org> wrote:
> > git pull
> > guix pull
> > guix environment -C guix
> > ./bootstrap
> > ./configure --localstatedir=/var/
> > make
>
> Apparently that didn't work on my pure x86_64 machine. It still kept
> not finding guile-json.
Hum? Weird... What does "guix describe" say?
And what does "guix show guix | grep guile-json" say?
> > If you do not want to update your profile, you can run:
> >
> > guix time-machine --commit=51eb3e113c478f0683e92412785ee82e56c45621
> > \ -- environment -C guix
> > ./bootstrap && ./configure --localstatedir=/var/ && make
> However that worked fine on that same machine.
It appears to me weird that this latter worked and not the previous
one. Did you really run "guix pull" because running "guix environment
-C guix" &co.?
All the best,
simon
next prev parent reply other threads:[~2020-10-02 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:07 How to build Guix to send a patch when Guix build fails? Denis 'GNUtoo' Carikli
2020-10-01 13:54 ` zimoun
2020-10-01 23:19 ` Denis 'GNUtoo' Carikli
2020-10-02 8:08 ` zimoun [this message]
2020-10-01 17:15 ` u-boot for beagleboard Vagrant Cascadian
2020-10-04 18:34 ` Danny Milosavljevic
2020-10-05 10:35 ` Miguel Ángel Arruga Vivas
2020-10-05 13:55 ` Ludovic Courtès
[not found] <mailman.2015.1601548807.2317.guix-devel@gnu.org>
2020-10-01 13:36 ` Guix-devel Digest, Vol 88, Issue 1 Jesse Gibbons
2020-10-01 14:01 ` zimoun
2020-10-01 14:53 ` How to build Guix to send a patch when Guix build fails? Jesse Gibbons
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='CAJ3okZ3nCFvk=XhtA22yUMbQ70+tqZO5Et3d6bOeoZZ2LN2pug@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=GNUtoo@cyberdimension.org \
--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).