unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: 41458@debbugs.gnu.org
Subject: bug#41458: Misleading error message when call guix command using pre-inst-env script
Date: Sat, 23 May 2020 17:46:06 +0200	[thread overview]
Message-ID: <87367q64e9.fsf@gnu.org> (raw)
In-Reply-To: <eede41df0c877faa186ea80188aa4054e96e2a9b.camel@korwin-zmijowski.fr> ("Jérémy Korwin-Zmijowski"'s message of "Fri, 22 May 2020 16:59:05 +0200")

Hi,

Jérémy Korwin-Zmijowski <jeremy@korwin-zmijowski.fr> skribis:

> Here is my command line history :
>
>    $ git clone https://git.savannah.gnu.org/git/guix.git
> $ cd guix
> $ guix environment --pure guix
> [dev]$ ./bootstrap && ./configure --localstatedir=/var && make &&
> exit
> …
> $ ./pre-inst-env guix build artanis
> guix: build: command not found
> Try `guix --help' for more information.

What probably happens here is that some of the required dependencies
provided in $GUILE_LOAD_PATH by ‘guix environment’ are not available
outside the environment.  As a result, loading the (guix scripts build)
module and its dependencies fail, which the machinery interprets as “no
such command”.

This is a development environment issue that cannot happen when using a
‘guix pull’-provided ‘guix’ command.  I would close it as “wontfix”
since, after all, it’s just one of the many ways one can end up with a
non-functional development environment.

WDYT?

Ludo’.




  reply	other threads:[~2020-05-23 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 14:59 bug#41458: Misleading error message when call guix command using pre-inst-env script Jérémy Korwin-Zmijowski
2020-05-23 15:46 ` Ludovic Courtès [this message]
2020-05-25 17:31   ` zimoun
2020-05-31 18:50     ` Jérémy Korwin-Zmijowski

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=87367q64e9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41458@debbugs.gnu.org \
    --cc=jeremy@korwin-zmijowski.fr \
    /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).