unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Adam Massmann <massmannak@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31940-done@debbugs.gnu.org
Subject: [bug#31940] [PATCH] gnu: Add Stalin.
Date: Mon, 25 Jun 2018 21:07:29 -0400	[thread overview]
Message-ID: <87y3f2we26.fsf@gmail.com> (raw)
In-Reply-To: <87efgur4cv.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 25 Jun 2018 22:36:00 +0200")

Hi Ludo,

ludo@gnu.org (Ludovic Courtès) writes:

> I applied the patch, but I added a FIXME about the fact that it’s
> “yogurt software” as Ricardo says: its “source” includes C files
> generated by itself, which are obviously not source code.  We try to
> avoid that, but OTOH we already have the same problem for several
> compilers, for instance MIT/GNU Scheme.
>
> From the README, previous versions were apparently bootstrapped using
> a separate Scheme->C compiler.  We could perhaps fix the problem by
> building one of these older versions of Stalin, and using it to build
> the latest one.  Would you like to give it a try?  (On this topic,
> don’t miss <http://bootstrappable.org/>.)

Thanks a lot for the code review and feedback - it's very helpful for me
as I learn. At first glance I think in this case, as you point out, we
should be able to use Scheme->C to generate the C files explicitly in
the build process. Also, some of the documentation suggests that
upstream *might* maintain a Scheme->C version for v0.11 and be willing
to share it, which would make it even easier.

I put it on my TODO list to dig in and try to fix it, but realistically
might not get to it until August due to work. Bootstrapping the build
should also extend the package to other architectures, which was
something I also wanted to do at some point.

> Anyway, thanks for the patch!

Thank you!

      reply	other threads:[~2018-06-26  1:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 18:35 [bug#31940] [PATCH] gnu: Add Stalin Adam Massmann
2018-06-25 20:36 ` bug#31940: " Ludovic Courtès
2018-06-26  1:07   ` Adam Massmann [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=87y3f2we26.fsf@gmail.com \
    --to=massmannak@gmail.com \
    --cc=31940-done@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).