unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Guix-devel Digest, Vol 88, Issue 1
Date: Thu, 1 Oct 2020 07:36:27 -0600	[thread overview]
Message-ID: <0ef4bcd4-14ee-7d60-d4c1-8245afc88ca0@gmail.com> (raw)
In-Reply-To: <mailman.2015.1601548807.2317.guix-devel@gnu.org>


> ------------------------------
>
> Message: 7
> Date: Thu, 1 Oct 2020 11:07:41 +0200
> From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
> To: guix-devel@gnu.org
> Subject: How to build Guix to send a patch when Guix build fails?
> Message-ID: <20201001110741.1bb8254c@primarylaptop.localdomain>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
Hello
>
> I'd like to send a patch to add a bootloader (u-boot) package for a
> single board computer. The patch is trivial and it's already
> ready.
>
> However before sending the patch, I'm supposed to build it within Guix
> source code and to test it.
>
> I've been trying many variations of 'guix environment --pure guix
> --ad-hoc <many packages>' during many many hours, but I still didn't
> manage to build Guix. I always have the failure that is in the
> build.log that I attached.
>
> I've the patch I attached on top of the following commit:
>> 51eb3e113c gnu: linux-libre 4.19: Update to 4.19.148.
> And I did the following commands last night when trying to build Guix:
>> $ guix pull
>> $ guix package -u
> 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
>
> Is there a command that is known to work to build Guix in a way that
> doesn't use any of the host packages?

Are you following the directions in the manual?

cd /path/to/local/guix/repository/with/changes
guix environment guix

(within the environment)

./bootstrap
#unfortunately the next critical line is not in the manual
./configure --localstatedir=/var
make
./pre-inst-env guix build <package-name>


> 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
>
> And it wouldn't pick Guix's guile-json, so I assume that for some
> reason it tried to use the host's packages somehow.

In that environment, check the value of $GUILE_LOAD_PATH.

I'm trying it, and I see it is empty. That can't be right...

>
> As I was told on IRC, building Guix from Guix latest revision is
> supposed to work. However if during the build it really uses
> packages from my host distribution (Parabola), then there might be some
> combination of packages that makes it fail, so here I hope that with
> the right guix environment command it would build.
>
> Denis.
-Jesse


       reply	other threads:[~2020-10-01 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2015.1601548807.2317.guix-devel@gnu.org>
2020-10-01 13:36 ` Jesse Gibbons [this message]
2020-10-01 14:01   ` Guix-devel Digest, Vol 88, Issue 1 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=0ef4bcd4-14ee-7d60-d4c1-8245afc88ca0@gmail.com \
    --to=jgibbons2357@gmail.com \
    --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).