all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Using CLISP instead of CCL to bootstrap SBCL
Date: Tue, 03 Sep 2019 14:43:24 +0200	[thread overview]
Message-ID: <87sgpdy2hf.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87woeptuys.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

>> I had a look into this, and it seems that CCL cannot currently be built
>> without itself :(
>
> That’s what Mark was hinting at,

Yes, what I meant is that upstream confirmed it.

> and that’s something people here and at
> <https://bootstrappable.org> have been trying hard to fix,

Do you mean that the people at bootstrappable have worked on CCL?

> so let’s not spoil it!  ;-)

What do you mean?

From the discussion with SBCL people, it seems that the best course of
action for now is to build against ECL or CLISP.
I'll test both, pick the one that's faster and merge.

What shall we do about CCL?  Keep it as "unbootstrappable" package?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-09-03 12:43 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgpdy2hf.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.