[9fans] lisp again.

[9fans] lisp again.

[Fernan Bolando]

lisp has been discuss in 9fans several times already

Anybody started porting clisp, gcl or any of the main lisp compilers?
I have been going at it on-and-off for some time never really
progressed, I was hoping
someone already started and got bored with it. I am hoping to use that
as a starting point.

where can I get the latest gcc port? maybe it's good enough to compile
one of the lisp compiler.


--
http://www.fernski.com

Re: [9fans] lisp again.

[LiteStar numnums]

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

Well, lisp != common lisp aside, I wouldn't mind a native CL system. I
haven't looked at the SBCL backend in quite sometime, but, assuming it's not
terribly insane, that would be a decent route. Most CL work that isn't
specific to one of the proprietary systems (Allegro, LispWorks, &c.) is
written with SBCL or, to a lesser extent, CCL. If anyone's interested in
working on a CL port to plan9, I'll start a lisp cabal, that can work on
other systems next.

I'll look today...


On Mon, Sep 7, 2009 at 3:29 AM, Fernan Bolando <fernanbolando@mailc.net>wrote:

> lisp has been discuss in 9fans several times already
>
> Anybody started porting clisp, gcl or any of the main lisp compilers?
> I have been going at it on-and-off for some time never really
> progressed, I was hoping
> someone already started and got bored with it. I am hoping to use that
> as a starting point.
>
> where can I get the latest gcc port? maybe it's good enough to compile
> one of the lisp compiler.
>
>
> --
> http://www.fernski.com
>
>


--
And in the "Only Prolog programmers will find this funny" department:

Q: How many Prolog programmers does it take to change a lightbulb?

A: No.
 -- Ovid

   "By cosmic rule, as day yields night, so winter summer, war peace, plenty
famine. All things change. Air penetrates the lump of myrrh, until the
joining bodies die and rise again in smoke called incense."

   "Men do not know how that which is drawn in different directions
harmonises with itself. The harmonious structure of the world depends upon
opposite tension like that of the bow and the lyre."

   "This universe, which is the same for all, has not been made by any god
or man, but it always has been, is, and will be an ever-living fire,
kindling itself by regular measures and going out by regular measures"
-- Heraclitus

[-- Attachment #2: Type: text/html, Size: 2365 bytes --]

Re: [9fans] lisp again.

[John Floren]

On Mon, Sep 7, 2009 at 8:47 AM, LiteStar numnums<litestar@gmail.com> wrote:
> Well, lisp != common lisp aside, I wouldn't mind a native CL system. I
> haven't looked at the SBCL backend in quite sometime, but, assuming it's not
> terribly insane, that would be a decent route. Most CL work that isn't
> specific to one of the proprietary systems (Allegro, LispWorks, &c.) is
> written with SBCL or, to a lesser extent, CCL. If anyone's interested in
> working on a CL port to plan9, I'll start a lisp cabal, that can work on
> other systems next.
>
> I'll look today...
[previous message and grotesque signature snipped]

One challenge with SBCL and some other implementations is that you
need a Common Lisp system already in place to compile them. I looked
into Clisp, which can be compiled with a C compiler, but after
fighting configure for a while I quit.

John
--
"Object-oriented design is the roman numerals of computing" -- Rob Pike

Re: [9fans] lisp again.

[Fernan Bolando]

On Mon, Sep 7, 2009 at 8:54 PM, John Floren<slawmaster@gmail.com> wrote:
> On Mon, Sep 7, 2009 at 8:47 AM, LiteStar numnums<litestar@gmail.com> wrote:
>> Well, lisp != common lisp aside, I wouldn't mind a native CL system. I
>> haven't looked at the SBCL backend in quite sometime, but, assuming it's not
>> terribly insane, that would be a decent route. Most CL work that isn't
>> specific to one of the proprietary systems (Allegro, LispWorks, &c.) is
>> written with SBCL or, to a lesser extent, CCL. If anyone's interested in
>> working on a CL port to plan9, I'll start a lisp cabal, that can work on
>> other systems next.
>>
>> I'll look today...
> [previous message and grotesque signature snipped]
>
> One challenge with SBCL and some other implementations is that you
> need a Common Lisp system already in place to compile them. I looked
> into Clisp, which can be compiled with a C compiler, but after
> fighting configure for a while I quit.
>

Last time I looked into this, I was comparing different version of a
common lisp systems to see which one might be easy enough to port
during the weekend. I remember I dropped to at least 3
1. gcl-1.0
2. ecl-8.12
3. clisp -- I guess I can remove this from my list

fernan


--
http://www.fernski.com

Re: [9fans] lisp again.

[LiteStar numnums]

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

I was going to use SBCL to cross compile SBCL for Plan9.

On Mon, Sep 7, 2009 at 8:54 AM, John Floren <slawmaster@gmail.com> wrote:

> On Mon, Sep 7, 2009 at 8:47 AM, LiteStar numnums<litestar@gmail.com>
> wrote:
> > Well, lisp != common lisp aside, I wouldn't mind a native CL system. I
> > haven't looked at the SBCL backend in quite sometime, but, assuming it's
> not
> > terribly insane, that would be a decent route. Most CL work that isn't
> > specific to one of the proprietary systems (Allegro, LispWorks, &c.) is
> > written with SBCL or, to a lesser extent, CCL. If anyone's interested in
> > working on a CL port to plan9, I'll start a lisp cabal, that can work on
> > other systems next.
> >
> > I'll look today...
> [previous message and grotesque signature snipped]
>
> One challenge with SBCL and some other implementations is that you
> need a Common Lisp system already in place to compile them. I looked
> into Clisp, which can be compiled with a C compiler, but after
> fighting configure for a while I quit.
>
> John
> --
> "Object-oriented design is the roman numerals of computing" -- Rob Pike
>
>


--
And in the "Only Prolog programmers will find this funny" department:

Q: How many Prolog programmers does it take to change a lightbulb?

A: No.
 -- Ovid

   "By cosmic rule, as day yields night, so winter summer, war peace, plenty
famine. All things change. Air penetrates the lump of myrrh, until the
joining bodies die and rise again in smoke called incense."

   "Men do not know how that which is drawn in different directions
harmonises with itself. The harmonious structure of the world depends upon
opposite tension like that of the bow and the lyre."

   "This universe, which is the same for all, has not been made by any god
or man, but it always has been, is, and will be an ever-living fire,
kindling itself by regular measures and going out by regular measures"
-- Heraclitus

[-- Attachment #2: Type: text/html, Size: 2516 bytes --]

Re: [9fans] lisp again.

[LiteStar numnums]

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

Clozure might be enough as well; it's C, but I've no idea how many POSIXisms
are in the source...

On Mon, Sep 7, 2009 at 9:19 AM, Fernan Bolando <fernanbolando@mailc.net>wrote:

> On Mon, Sep 7, 2009 at 8:54 PM, John Floren<slawmaster@gmail.com> wrote:
> > On Mon, Sep 7, 2009 at 8:47 AM, LiteStar numnums<litestar@gmail.com>
> wrote:
> >> Well, lisp != common lisp aside, I wouldn't mind a native CL system. I
> >> haven't looked at the SBCL backend in quite sometime, but, assuming it's
> not
> >> terribly insane, that would be a decent route. Most CL work that isn't
> >> specific to one of the proprietary systems (Allegro, LispWorks, &c.) is
> >> written with SBCL or, to a lesser extent, CCL. If anyone's interested in
> >> working on a CL port to plan9, I'll start a lisp cabal, that can work on
> >> other systems next.
> >>
> >> I'll look today...
> > [previous message and grotesque signature snipped]
> >
> > One challenge with SBCL and some other implementations is that you
> > need a Common Lisp system already in place to compile them. I looked
> > into Clisp, which can be compiled with a C compiler, but after
> > fighting configure for a while I quit.
> >
>
> Last time I looked into this, I was comparing different version of a
> common lisp systems to see which one might be easy enough to port
> during the weekend. I remember I dropped to at least 3
> 1. gcl-1.0
> 2. ecl-8.12
> 3. clisp -- I guess I can remove this from my list
>
> fernan
>
>
> --
> http://www.fernski.com
>
>


--
And in the "Only Prolog programmers will find this funny" department:

Q: How many Prolog programmers does it take to change a lightbulb?

A: No.
 -- Ovid

   "By cosmic rule, as day yields night, so winter summer, war peace, plenty
famine. All things change. Air penetrates the lump of myrrh, until the
joining bodies die and rise again in smoke called incense."

   "Men do not know how that which is drawn in different directions
harmonises with itself. The harmonious structure of the world depends upon
opposite tension like that of the bow and the lyre."

   "This universe, which is the same for all, has not been made by any god
or man, but it always has been, is, and will be an ever-living fire,
kindling itself by regular measures and going out by regular measures"
-- Heraclitus

[-- Attachment #2: Type: text/html, Size: 3110 bytes --]

Re: [9fans] lisp again.

[Iruata Souza]

On Mon, Sep 7, 2009 at 9:54 AM, John Floren<slawmaster@gmail.com> wrote:
> On Mon, Sep 7, 2009 at 8:47 AM, LiteStar numnums<litestar@gmail.com> wrote:
>> Well, lisp != common lisp aside, I wouldn't mind a native CL system. I
>> haven't looked at the SBCL backend in quite sometime, but, assuming it's not
>> terribly insane, that would be a decent route. Most CL work that isn't
>> specific to one of the proprietary systems (Allegro, LispWorks, &c.) is
>> written with SBCL or, to a lesser extent, CCL. If anyone's interested in
>> working on a CL port to plan9, I'll start a lisp cabal, that can work on
>> other systems next.
>>
>> I'll look today...
> [previous message and grotesque signature snipped]
>
> One challenge with SBCL and some other implementations is that you
> need a Common Lisp system already in place to compile them. I looked
> into Clisp, which can be compiled with a C compiler, but after
> fighting configure for a while I quit.
>

maybe the bootstrap can be done with linuxemu.

iru

Re: [9fans] lisp again.

[erik quanstrom]

> maybe the bootstrap can be done with linuxemu.

wouldn't that just give you yet another linux elf binary?

- erik

Re: [9fans] lisp again.

[Iruata Souza]

On Mon, Sep 7, 2009 at 10:53 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>> maybe the bootstrap can be done with linuxemu.
>
> wouldn't that just give you yet another linux elf binary?
>

you are right. it must know how to compile correct a.out(6).

iru