From: John J Foerch <jjfoerch@earthlink.net>
To: help-guix@gnu.org
Subject: Re: chicken scheme
Date: Thu, 30 Jun 2016 17:43:21 -0400 [thread overview]
Message-ID: <87vb0qbbeu.fsf@hecubus.retroj.net> (raw)
In-Reply-To: 87shvumkp0.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:
> 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’.
Hello Ludovic,
Installing gcc-toolchain helped, and there are no more compilation
errors. Another error came up in trying to install the built files.
Here is my log:
$ chicken-install matchable
retrieving ...
connecting to host "chicken.kitten-technologies.co.uk", port 80 ...
requesting "/henrietta.cgi?name=matchable&mode=default" ...
reading response ...
HTTP/1.1 200 OK
Date: Thu, 30 Jun 2016 21:36:20 GMT
Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.8.10 PHP/5.4.32 mod_fastcgi/2.4.6
Connection: close
Transfer-Encoding: chunked
Content-Type: text/plain
reading chunks ...
reading files ...
./match-simple.scm
./match.scm
./matchable-test.scm
./matchable.meta
./matchable.scm
./matchable.setup
matchable located at /tmp/temp112c.2170/matchable
checking platform for `matchable' ...
checking dependencies for `matchable' ...
install order:
("matchable")
installing matchable:3.6 ...
changing current directory to /tmp/temp112c.2170/matchable
'/gnu/store/avfhy6zgqmxgbvjrava16qyh60y6xwzv-chicken-4.11.0/bin/csi' -bnq -setup-mode -e "(require-library setup-api)" -e "(import setup-api)" -e "(setup-error-handling)" -e "(extension-name-and-version '(\"matchable\" \"3.6\"))" 'matchable.setup'
'/gnu/store/avfhy6zgqmxgbvjrava16qyh60y6xwzv-chicken-4.11.0/bin/csc' -feature compiling-extension -setup-mode -s -O3 -d0 matchable.scm -j matchable
'/gnu/store/avfhy6zgqmxgbvjrava16qyh60y6xwzv-chicken-4.11.0/bin/csc' -feature compiling-extension -setup-mode -s -O3 -d0 matchable.import.scm
cp -r 'matchable.so' '/gnu/store/avfhy6zgqmxgbvjrava16qyh60y6xwzv-chicken-4.11.0/var/lib/chicken/8/matchable.so'
cp: cannot create regular file ‘/gnu/store/avfhy6zgqmxgbvjrava16qyh60y6xwzv-chicken-4.11.0/var/lib/chicken/8/matchable.so’: Read-only file system
Error: shell command failed with nonzero exit status 256:
cp -r 'matchable.so' '/gnu/store/avfhy6zgqmxgbvjrava16qyh60y6xwzv-chicken-4.11.0/var/lib/chicken/8/matchable.so'
Error: shell command terminated with nonzero exit code
17920
"'/gnu/store/avfhy6zgqmxgbvjrava16qyh60y6xwzv-chicken-4.11.0/bin/csi' -bnq -setu...
--
John Foerch
next prev parent reply other threads:[~2016-06-30 21:43 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 [this message]
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=87vb0qbbeu.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).