From: zimoun <zimon.toutoune@gmail.com>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>, guix-devel@gnu.org
Subject: Re: How to build Guix to send a patch when Guix build fails?
Date: Thu, 01 Oct 2020 15:54:06 +0200 [thread overview]
Message-ID: <86o8lm3vcx.fsf@gmail.com> (raw)
In-Reply-To: <20201001110741.1bb8254c@primarylaptop.localdomain>
Dear,
On Thu, 01 Oct 2020 at 11:07, Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> I did it with the following hardware and distributions configurations:
> - Architecture: i686
> - Host distribution: Parabola i686 with a x86_64 kernel (5.7.2-gnu-1-64)
> - Guix architecture: i686
I do not know what happens here, since i686 and x86_64.
> I also tried on another machine with the following configuration:
> - Architecture: x86-64
> - Host distribution: Parabola x86_64 without guile-json installed
> - Guix architecture: x86_64
> - Guix environment command: 'guix environment --pure guix --ad-hoc
> guile-json
On this machine, the following commands should work:
git pull
guix pull
guix environment -C guix
./bootstrap
./configure --localstatedir=/var/
make
The issue with ’guile-json’ could come from the Guix version used to
create the environment, that’s why before you need to do a “guix pull”.
It does not matter of the package is already installed or not; that’s
the point to “guix environment guix” to fetch all the requirements.
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
Hope that helps,
simon
next prev parent reply other threads:[~2020-10-01 13:54 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 [this message]
2020-10-01 23:19 ` Denis 'GNUtoo' Carikli
2020-10-02 8:08 ` zimoun
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=86o8lm3vcx.fsf@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).