From: "Thompson, David" <dthompson2@worcester.edu>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 22366@debbugs.gnu.org
Subject: bug#22366: [EXT] Bug#22366 Status? Chicken Scheme release tarballs ship non-source C code
Date: Thu, 14 May 2020 15:04:45 -0400 [thread overview]
Message-ID: <CAJ=RwfYs5AmO=nsEEqVJW0chcTCq94iBapOd8ab8ECKh9odTjA@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ2MQ0vfbUYMkk7iFgua6cnEYF94r4pVq6frQfZe0aOGFA@mail.gmail.com>
On Tue, May 12, 2020 at 7:33 PM zimoun <zimon.toutoune@gmail.com> wrote:
>
> Dear David,
>
> The bug report [1] opened more than 4 years ago about the Chicken
> bootstrapping is still pending.
>
> I am not sure to understand these lines; quoting you [1]:
>
> <<
> Generated from optimizer.scm by the CHICKEN compiler
>
> This is *not* source code, it's a binary disguised as C source code.
> >>
>
> Why is it an issue for bootstrappability?
Because software is not bootstrappable if it requires taking for
granted files that are not source code. In this case, it is these C
files. These files are not source code because they are machine
generated. In order to generate these files, you need a Chicken
Scheme compiler. Therefore, you cannot build Chicken Scheme from
source code without already having Chicken Scheme, which makes it
non-bootstrappable. I have not kept track of this issue but my
understanding was that the Chicken developers do not care (which is
unfortunately a very common reaction from developers of self-hosted
compilers) but it is nevertheless a bootstrapping issue.
> Thank you in advance for any comments.
> Or could this bug report be closed?
I don't think this can be closed because it is still an issue.
- Dave
next prev parent reply other threads:[~2020-05-14 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 18:54 bug#22366: Chicken Scheme release tarballs ship non-source C code Thompson, David
2020-05-12 23:33 ` bug#22366: Status? " zimoun
2020-05-14 19:04 ` Thompson, David [this message]
2020-05-15 10:15 ` bug#22366: [EXT] Bug#22366 " zimoun
2021-08-17 9:13 ` bug#22366: " Mario Domenech Goulart
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='CAJ=RwfYs5AmO=nsEEqVJW0chcTCq94iBapOd8ab8ECKh9odTjA@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=22366@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.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 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).