From: ludo@gnu.org (Ludovic Courtès)
To: John J Foerch <jjfoerch@earthlink.net>
Cc: help-guix@gnu.org
Subject: Re: chicken scheme
Date: Thu, 30 Jun 2016 23:27:23 +0200 [thread overview]
Message-ID: <87shvumkp0.fsf@gnu.org> (raw)
In-Reply-To: <871t3ecx0f.fsf@hecubus.retroj.net> (John J. Foerch's message of "Thu, 30 Jun 2016 15:11:28 -0400")
Hi,
John J Foerch <jjfoerch@earthlink.net> skribis:
> I ran into some problems when installing CHICKEN Scheme on my new GuixSD
> system. After installing the chicken package, 'chicken-install' failed
> because gcc was not found on the system. In the package definition for
> chicken, gcc is listed as a native-input, but from what I understand it
> should either be a regular input or a propagated-input, because CHICKEN
> uses gcc to compile scheme programs.
Good point. Perhaps CHICKEN should keep references to the GCC toolchain
that was used to build it, or propagate it. OTOH, it can in theory use
whatever GCC that it finds in $PATH, and people using the interpreter
don’t need GCC, which would be an argument in favor of the status quo.
Thoughts?
> I installed gcc separately, and then a test of chicken-install produced
> this error:
>
> linux/limits.h: No such file or directory #include <linux/limits.h>
>
> I was testing chicken-install with this command:
>
> $ chicken-install matchable
Could you run:
guix package -r gcc -i gcc-toolchain
and try again?
The ‘gcc-toolchain’ package provides GCC, Binutils, glibc, and a wrapper
around ‘ld’ (it makes sure every library linked against is added to the
RUNPATH.)
Thanks for reporting the issue,
Ludo’.
next prev parent reply other threads:[~2016-06-30 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 19:11 chicken scheme John J Foerch
2016-06-30 21:27 ` Ludovic Courtès [this message]
2016-06-30 21:43 ` John J Foerch
2016-07-01 9:36 ` Ludovic Courtès
2016-07-01 12:11 ` John J Foerch
2016-07-01 13:27 ` Thompson, David
2016-07-01 19:52 ` Ludovic Courtès
2016-07-01 20:22 ` John J Foerch
2016-07-02 10:21 ` Ludovic Courtès
2016-07-17 14:22 ` John J Foerch
2016-07-17 17:45 ` Ludovic Courtès
2016-06-30 22:05 ` John J Foerch
2016-07-01 9:39 ` Ludovic Courtès
2016-07-01 12:16 ` John J Foerch
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=87shvumkp0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=jjfoerch@earthlink.net \
/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.
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).