From mboxrd@z Thu Jan 1 00:00:00 1970 From: John J Foerch Subject: Re: chicken scheme Date: Thu, 30 Jun 2016 18:05:36 -0400 Message-ID: <87oa6ibadr.fsf@hecubus.retroj.net> References: <871t3ecx0f.fsf@hecubus.retroj.net> <87shvumkp0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60885) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bIk5p-0006A8-33 for help-guix@gnu.org; Thu, 30 Jun 2016 18:05:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bIk5l-0008VN-Ox for help-guix@gnu.org; Thu, 30 Jun 2016 18:05:52 -0400 Received: from plane.gmane.org ([80.91.229.3]:52407) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bIk5l-0008VJ-IG for help-guix@gnu.org; Thu, 30 Jun 2016 18:05:49 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bIk5i-0000Ea-C9 for help-guix@gnu.org; Fri, 01 Jul 2016 00:05:46 +0200 Received: from 152.160.144.141 ([152.160.144.141]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Jul 2016 00:05:46 +0200 Received: from jjfoerch by 152.160.144.141 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Jul 2016 00:05:46 +0200 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org ludo@gnu.org (Ludovic Courtès) writes: > > 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 don't have enough experience with guix to give definite advice on this, but chicken does present a couple of unique issues. I think that having gcc available is essential to chicken's purpose, as one is not likely to only use the interpreter. Installing extensions requires C compilation, and if one is not installing extensions and not using chicken's compiler, then one might as well be using any old scheme off the street ;-) If the gcc-toolchain were kept in reference (but not in the profile), that may be enough. The chicken compiler has options (and/or environment variables) to use another gcc if desired, so people who want to use another gcc than the one used to build chicken can still do so. Some chicken extensions install executable programs (for example hyde). On other OSes they would normally be installed to /usr/local/bin. Obviously this would be different for guix. -- John Foerch