unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 32316@debbugs.gnu.org
Subject: bug#32316: Build failure with installed guix that does not happen with pre-inst-env
Date: Mon, 30 Jul 2018 21:42:22 +0200	[thread overview]
Message-ID: <20180730214222.4c08be42@alma-ubu> (raw)
In-Reply-To: <m1sh401yx5.fsf@fastmail.net>

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Hi Konrad,

thanks for the precise error report.

On Mon, 30 Jul 2018 18:16:54 +0200
Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:

> Dear Guix experts,
> 
> When updating my Guix installation after three weeks of absence, I
> noticed a build failure:
> 
>    $ guix pull –commit=de596e99549d7764f370ab2ed3b756f620b1f23d
>    $ guix build racket

Could it be the case that in your `guix build ...` you are not using
the guix you pulled?

What does `guix --version` say?

Where does `which guix` point to?

It should point to

~/.config/guix/current/bin/guix

I suspect you have an older version of Guix (i.e. "before the new
implementation") in your $PATH with a higher precedence (more to the
beginning of the $PATH variable). See what `echo $PATH` says. If that
is the case, adapt your path.

HTH,

Björn


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-07-30 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 16:16 bug#32316: Build failure with installed guix that does not happen with pre-inst-env Konrad Hinsen
2018-07-30 19:42 ` Björn Höfling [this message]
2018-07-31  9:42   ` Konrad Hinsen
2018-07-31 10:04     ` Julien Lepiller
2018-08-22 15:51 ` bug#32316: Thanks! Konrad Hinsen

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=20180730214222.4c08be42@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=32316@debbugs.gnu.org \
    --cc=konrad.hinsen@fastmail.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. 
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).