From: John J Foerch <jjfoerch@earthlink.net>
To: help-guix@gnu.org
Subject: Re: chicken scheme
Date: Fri, 01 Jul 2016 08:16:19 -0400 [thread overview]
Message-ID: <87a8i1blkc.fsf@hecubus.retroj.net> (raw)
In-Reply-To: 87vb0plmst.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:
> John J Foerch <jjfoerch@earthlink.net> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>> 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 ;-)
>
> Right, makes sense. :-)
>
>> 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.
>
> OK. Then I guess we should adjust our ‘chicken’ package so that it
> hard-codes the absolute file name of ‘gcc’ and ‘ld’. Would you like to
> give it a try?
>
Sure!
>> 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.
>
> This part doesn’t sound Guix-dependent. It’s more about whether
> non-root users can install to, say, ~/.local, or whether only root can
> install (to /usr/local/bin or similar.) WDYT?
>
Sorry, I don't really understand the issues at hand well enough yet to
comment. I have been looking at 'guix import', as I said in my other
message, and I now wonder if a package importer is the best way forward,
in accordance with the guix spirit.
--
John Foerch
prev parent reply other threads:[~2016-07-01 12:20 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
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 [this message]
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=87a8i1blkc.fsf@hecubus.retroj.net \
--to=jjfoerch@earthlink.net \
--cc=help-guix@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.
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).