From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Using CLISP instead of CCL to bootstrap SBCL
Date: Fri, 30 Aug 2019 10:39:04 +0200 [thread overview]
Message-ID: <87o9079hef.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87d0gnljf6.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Hi Mark,
First of all, thanks for your interest in Next! :)
If you look at the sbcl package, you'll see this comment which I
copy-pasted from SBCL "INSTALL" file:
--8<---------------cut here---------------start------------->8---
;; From INSTALL:
;; Supported build hosts are:
;; SBCL
;; CMUCL
;; CCL (formerly known as OpenMCL)
;; ABCL (recent versions only)
;; CLISP (only some versions: 2.44.1 is OK, 2.47 is not)
;; XCL
--8<---------------cut here---------------end--------------->8---
The point was 2-fold:
- CLISP seems unreliable.
- SBCL takes ages to compile with it :p (I know, this is mostly practical.)
We can ask the SBCL developers to let us know if they think CLISP can be
re-approved, but as far as I understand, it's mostly untested.
Another solution would be to bootstrap SBCL or CCL
differently. I haven't looked into the details, but there may be some
older version of CCL or SBCL that could be build from C or CLISP
reliably, then use those versions to build the latest CCL and SBCL.
I can look into maybe later next week (no promise, September is going to
be tight for me).
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-08-30 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 22:01 Using CLISP instead of CCL to bootstrap SBCL Mark H Weaver
2019-08-30 8:39 ` Pierre Neidhardt [this message]
2019-09-02 10:16 ` Pierre Neidhardt
2019-09-02 12:44 ` Pierre Neidhardt
2019-09-02 13:01 ` Pierre Neidhardt
2019-09-03 12:39 ` Ludovic Courtès
2019-09-03 12:43 ` Pierre Neidhardt
2019-09-05 9:46 ` Pierre Neidhardt
2019-09-05 20:07 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2019-08-30 12:33 Guillaume Le Vaillant
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=87o9079hef.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).