all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <bavier@cray.com>
Cc: 30879@debbugs.gnu.org
Subject: bug#30879: Commit bc499b113 broke guix on guile@2.0.14, improper <operating-system> field initialization
Date: Wed, 21 Mar 2018 22:04:00 +0100	[thread overview]
Message-ID: <87y3ildttr.fsf@gnu.org> (raw)
In-Reply-To: <20180321151642.GN105827@pe06.us.cray.com> (Eric Bavier's message of "Wed, 21 Mar 2018 10:16:42 -0500")

Eric Bavier <bavier@cray.com> skribis:

> On Wed, Mar 21, 2018 at 12:12:02AM +0100, Ludovic Courtès wrote:
>
>> That sounds a lot like regular ABI breakage: a new <operating-system>
>> field was added but gnu/tests/base.go wasn’t rebuilt, and thus was
>> expecting the previous struct layout.
>> 
>> Does “rm gnu/tests/base.go && make” suffice to fix this issue?
>
> No, it doesn't help.  Previously I had been running "make clean-go"
> before each "make.
>
> The error/backtrace is issued when build-aux/compile-all.scm tries to
> load gnu/tests/base.scm, before it even gets to compilation.

Oh, can you “rm -rf ~/.cache/guile”?

One thing that could be an issue is that (gnu system install) loads
‘examples/bare-bones.tmpl’.  Thus ‘bare-bones.tmpl.go’ ends up in
~/.cache/guile and could be out of sync.

Thanks,
Ludo’.

  reply	other threads:[~2018-03-21 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 15:43 bug#30879: Commit bc499b113 broke guix on guile@2.0.14, improper <operating-system> field initialization Eric Bavier
2018-03-20 23:12 ` Ludovic Courtès
2018-03-21 15:16   ` Eric Bavier
2018-03-21 21:04     ` Ludovic Courtès [this message]
2018-03-21 21:14       ` Eric Bavier
2018-03-21 23:04         ` Ludovic Courtès
2018-03-22 14:45           ` Eric Bavier
2018-03-22 16:19             ` Ludovic Courtès
2018-03-29 17:06               ` Eric Bavier
2018-05-15  9:20             ` Ludovic Courtès
2018-04-11 18:42 ` Eric Bavier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3ildttr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30879@debbugs.gnu.org \
    --cc=bavier@cray.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.