From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: chicken scheme
Date: Thu, 30 Jun 2016 23:27:23 +0200
Message-ID: <87shvumkp0.fsf@gnu.org>
References: <871t3ecx0f.fsf@hecubus.retroj.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54904)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bIjUm-0005fB-EH
	for help-guix@gnu.org; Thu, 30 Jun 2016 17:27:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bIjUi-0008Ik-6U
	for help-guix@gnu.org; Thu, 30 Jun 2016 17:27:35 -0400
In-Reply-To: <871t3ecx0f.fsf@hecubus.retroj.net> (John J. Foerch's message of
	"Thu, 30 Jun 2016 15:11:28 -0400")
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-guix/>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
To: John J Foerch <jjfoerch@earthlink.net>
Cc: help-guix@gnu.org

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=E2=80=99t need GCC, which would be an argument in favor of the status q=
uo.

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 =E2=80=98gcc-toolchain=E2=80=99 package provides GCC, Binutils, glibc, =
and a wrapper
around =E2=80=98ld=E2=80=99 (it makes sure every library linked against is =
added to the
RUNPATH.)

Thanks for reporting the issue,
Ludo=E2=80=99.