[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] Compilation Methodology Overview and a Specific Pr

From: David MENTRE
Subject: Re: [Axiom-developer] Compilation Methodology Overview and a Specific Problem
Date: Wed, 14 Jul 2004 20:31:43 +0200
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Hello Mark,

I cannot remember if anybody has replied to your questions, so I give
them a try:

"Mark E. Fenner" <address@hidden> writes:

> Why does axiom build its own LISP(s) instead of using LISP(s) that I may 
> already have on my system?  Is this the different characteristics of 
> different LISPs mentioned in the top-level README file?  

Axiom has its own Lisp to have a known the build environment and because
Axiom needs to patch the lisp core system for its own purpose (socket
extension). This might change in the future but is not in the short term

However, it is possible to make Axiom rely on an external Lisp
(GCL). Camm Maguire is doing it for the Debian Axiom package.

> Is there any preference of using LISP versions that are 1) the same or 2) 
> different from what I have on my machine?  For example, if I have gcl 2.5.2 
> installed on my machine, should I necessarily choose GCLVERSION=gcl-2.5.2 in 
> my makefile (or from an export GCLVERSION)?

You should use the default lisp in the current sources of Axiom. 

> Finally,  I believe the top level Makefile.dvi description states that gcl 
> 2.4.1 is the default gcl version.  The CVS toplevel Makefile seems to have 
> the GCLVERSION=gcl-2.6.2 line uncommented.  Is this as intended or do the 
> docs need updated?

The docs need updates. We will gladly accept any diff -Naur of your

David MENTRE <address@hidden> --

reply via email to

[Prev in Thread] Current Thread [Next in Thread]