From: raingloom <raingloom@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43976@debbugs.gnu.org
Subject: [bug#43976] [PATCH] Chicken build system + some example eggs
Date: Sat, 21 Nov 2020 21:45:43 +0100 [thread overview]
Message-ID: <20201121214543.37c27429@riseup.net> (raw)
In-Reply-To: <20201120055117.7cb76230@riseup.net>
On Fri, 20 Nov 2020 05:51:17 +0100
raingloom <raingloom@riseup.net> wrote:
> Possibly more important: I noticed some warnings in some builds about
> cp(1). So far it hasn't caused any issues. Gonna fix this, then I
> think it'll be mergeable.
Seems to be a srfi-18 specific issue, so I'm calling
chicken-build-system final for now. You can merge it if it stands up to
a review.
The other eggs also seem fine, srfi-18 just has a somewhat shoddily
written auxiliary build script to generate some type information,
probably based on the current Chicken version? I'm not sure what it's
doing to be honest. It doesn't fail to build because the script doesn't
check for errors, which is why it took a while to notice it.
This is why we always `set -e` in our Bash scripts, kids.
Anyways, all other eggs seem to be fine, and none of them depend on
srfi-18.
next prev parent reply other threads:[~2020-11-21 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 8:52 [bug#43976] [PATCH] Chicken build system + some example eggs raingloom
2020-10-18 16:10 ` Ludovic Courtès
2020-11-20 4:51 ` raingloom
2020-11-21 11:23 ` Ludovic Courtès
2020-11-21 20:45 ` raingloom [this message]
2020-11-21 20:58 ` Efraim Flashner
2020-11-21 22:13 ` raingloom
2020-11-22 23:12 ` raingloom
2020-11-24 20:22 ` raingloom
2020-11-27 9:09 ` Ludovic Courtès
2020-12-01 4:14 ` raingloom
2020-12-03 16:04 ` bug#43976: " 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=20201121214543.37c27429@riseup.net \
--to=raingloom@riseup.net \
--cc=43976@debbugs.gnu.org \
--cc=ludo@gnu.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).