From: "Thompson, David" <dthompson2@worcester.edu>
To: 22366@debbugs.gnu.org
Subject: bug#22366: Chicken Scheme release tarballs ship non-source C code
Date: Wed, 13 Jan 2016 13:54:37 -0500 [thread overview]
Message-ID: <CAJ=RwfbrqdFqnSAMHDHG_6vsSr7R3QcPGjg6Eu2bzseBjTaeNQ@mail.gmail.com> (raw)
Because Chicken Scheme's compiler is self-hosting, and because it
compiles to C as an intermediate form, the maintainers circumvented
the bootstrapping problem by shipping generated C code for the
compiler. Many *.c files feature a comment that starts like this:
Generated from optimizer.scm by the CHICKEN compiler
This is *not* source code, it's a binary disguised as C source code.
To resolve this bug, we need to delete these generated files from the
source tarball and figure out how to bootstrap Chicken without them.
Maybe someone who actively uses Chicken knows how to do this?
- Dave
next reply other threads:[~2016-01-13 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 18:54 Thompson, David [this message]
2020-05-12 23:33 ` bug#22366: Status? Chicken Scheme release tarballs ship non-source C code zimoun
2020-05-14 19:04 ` bug#22366: [EXT] Bug#22366 " Thompson, David
2020-05-15 10:15 ` 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=RwfbrqdFqnSAMHDHG_6vsSr7R3QcPGjg6Eu2bzseBjTaeNQ@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=22366@debbugs.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).