public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] dev-lisp
Date: Thu Aug  2 20:08:02 2001	[thread overview]
Message-ID: <20010803040730.B24491@prosalg.no> (raw)

Hi gang.

I'm going to celebrate my newfound gentoo developer status by not doing
anything on gentoo at all this weekend. I'm heading out of the country for
a much-earned relaxation weekend in the Scottish highlands.

When I get back, I'm going to suggest we make a dev-lisp category. I have
two working ebuilds for that category currently: ecls-0.2 and gcl-2.4.0

I'm working on sbcl and cmucl, but here is a small problem: Neither sbcl
nor cmucl can be bootstrapped from C (or any lisp implementation we can
compile using only the C compiler). sbcl must be bootstrapped from itself
of cmucl. cmucl must be bootstrapped from itself.

What this means is that to install cmucl og sbcl, we have to first get an
x86 binary for the particular compiler, then run that as the bootstrapping
compiler.

This primarily means we will fetch and run a binary, which I don't think
is being done anywhere (except if you consider the gentoo build iso
itself as a bootstrap) until now, and that this binary will only run on
x86.

I don't necessarily see a problem with this, but it's a bit different from
all the other packages we have.

Comments, suggestions ? (I'll read them when I get back on sunday
evening).

(In the distant future, sbcl might be able to bootstrap on ecls, and cmucl
might be able to bootstrap on sbcl, so we could theoretically built it all
completely from sources for the die-hard purists, but don't hold your
breath.)

Regards,

Karl T



             reply	other threads:[~2001-08-03  2:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 20:08 Karl Trygve Kalleberg [this message]
2001-08-02 22:12 ` [gentoo-dev] dev-lisp Daniel Robbins
2001-08-03  1:20 ` Dan Armak
2001-08-05 18:23   ` Karl Trygve Kalleberg
2001-08-03  6:53 ` Terje Kvernes

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=20010803040730.B24491@prosalg.no \
    --to=karltk@prosalg.no \
    --cc=gentoo-dev@cvs.gentoo.org \
    --cc=gentoo-dev@gentoo.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