unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 26791-done@debbugs.gnu.org
Subject: bug#26791: Attempt to apply a string as a procedure during Hydra evaluation
Date: Sun, 07 May 2017 11:35:39 +0200	[thread overview]
Message-ID: <8760hdqaac.fsf@gnu.org> (raw)
In-Reply-To: <20170507084326.3e5be220@scratchpost.org> (Danny Milosavljevic's message of "Sun, 7 May 2017 08:43:26 +0200")

Hi,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> I think it always works (also without compilation) when I move the boot-parameters record definition up in gnu/system.scm (so it comes before its clients).

Yeah I just pushed that as 8e815c5b6903a545c46b674c1cd1cc3180f835db.

The thing is that ‘boot-parameters’ is a macro, so it must be defined
before used.

Because of the way build-aux/compile-all.scm builds things (first loads
modules, then builds them), this error would not show up because the
macro would have been defined during the load phase.  However evaluation
on Hydra relies on auto-compilation, which does things the “normal” way.

I’ve started an evaluation of ‘master’ on Hydra.

Thanks,
Ludo’.

  reply	other threads:[~2017-05-07  9:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06  0:40 bug#26791: Attempt to apply a string as a procedure during Hydra evaluation Mark H Weaver
2017-05-06  7:46 ` Mathieu Othacehe
2017-05-06 22:44   ` Mark H Weaver
2017-05-07  6:43 ` Danny Milosavljevic
2017-05-07  9:35   ` Ludovic Courtès [this message]
2017-05-07 21:31     ` Leo Famulari
2017-05-07 22:37       ` Mark H Weaver
2017-05-08 12:40         ` Ludovic Courtès
2017-05-07 22:23     ` Mark H Weaver
2017-05-07 10:11 ` bug#26791: Hydra doesn't run make before using Guix Danny Milosavljevic
2017-05-09 21:29   ` Ludovic Courtès

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=8760hdqaac.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26791-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).