From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: ABI break!
Date: Wed, 18 Jan 2017 22:25:38 +0100 [thread overview]
Message-ID: <878tq883hp.fsf@gnu.org> (raw)
In-Reply-To: <20170118061703.GA26238@jocasta.intra> (John Darrington's message of "Wed, 18 Jan 2017 07:17:04 +0100")
John Darrington <john@darrington.wattle.id.au> skribis:
> On Tue, Jan 17, 2017 at 11:52:35PM +0100, Ludovic Court??s wrote:
> ludo@gnu.org (Ludovic Court??s) skribis:
>
> > Pushed with tests as 384344198dcaa97847e66d3dd82f279ede08d690.
>
> And if you get a weird error when running ???make??? about
> ???file-system-needed-for-boot????, just run:
>
> rm gnu/system.go && make
>
> This is because of an ABI break: ???file-system-needed-for-boot???? was a
> macro and now is a procedure.
>
> Surely this means that the Makefile is wrong?
>
> It should recognise that gnu/system.scm has changed and rebuild gnu/system.go accordingly.
gnu/system.scm has not changed; gnu/system/file-system.scm did.
Guile modules are composed at run time for the most part, so when you
change one, you don’t have to rebuild those that use it.
However, you do have to recompile them if they rely on it for macros and
those macros have changed or are no longer macros.
This is what happened here.
Ludo’.
prev parent reply other threads:[~2017-01-18 21:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 20:01 [PATCH] gnu: Mark /gnu/store as needed for boot John Darrington
2017-01-13 8:59 ` Chris Marusich
2017-01-13 11:01 ` John Darrington
2017-01-14 21:30 ` Ludovic Courtès
2017-01-15 6:32 ` John Darrington
2017-01-15 9:53 ` David Craven
2017-01-15 11:18 ` John Darrington
2017-01-15 22:24 ` Ludovic Courtès
2017-01-16 12:46 ` John Darrington
2017-01-16 22:28 ` Ludovic Courtès
2017-01-17 22:52 ` ABI break! Ludovic Courtès
2017-01-18 6:17 ` John Darrington
2017-01-18 10:56 ` David Craven
2017-01-18 21:25 ` Ludovic Courtès [this message]
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=878tq883hp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
--cc=john@darrington.wattle.id.au \
/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).