Re: [Axiom-developer] GCL version

[Camm Maguire]

Greetings!  (I'm away until 6/1, but am managing to read this remotely
today.  Unfortunately, communication with me might be unreliable until
6/1.) 

Just a quick note to say that the best intermediary step in my
opinion is to fire up GCL, do all your (make-package 's, save the
system, and use this to build axiom with the traditional code until
the in-package issue gets worked out.  Maybe someone could post a list
of package definitions here?  As Tim says, this obviously won't affect
the compiler generated code that users may invoke on an ad-hoc basis,
but the basic packages for the Axiom build should be known ahead of
time. 

Take care,


root <address@hidden> writes:

> Well I originally tried to run with GCL 2.5 and was not 
> successful. I sent a note to Camm (the GCL lead) and he
> mentioned that Common Lisp had changed since Axiom was last
> released (on AKCL). The key problem has to do with the package
> issue. In detail the problem is that the code generally does
> an
>  
> (in-package 'foo)
> 
> at the top of each file. In prior versions of common lisp this
> would create the package foo if it did not exist. Now you must do:
> 
> (make-package 'foo)
> (in-package 'foo)
> 
> in order to have the same effect. I backed off from fixing this 
> issue because it involves more than just fixing the lisp code.
> Axiom generates common lisp (well, some really strange version
> of common lisp because it is an akcl port of a vmlisp port of
> a maclisp version). Thus we need to find and fix the compiler(s)
> that exist in the system.
> 
> As to the "non visibility of BOOTTRAN package in the compilation
> enviroment" it should be possible to create a lisp image that
> includes BOOTTRAN by doing this in a lisp image:
> 
> (make-package "BOOTTRAN")
> (system-savesystem "lisp")
> 
> I'll experiment with it tonight and get back to you on it.
> 
> As to the algebra bug... it continues. I've got it cornered
> but haven't been able to look at it this week. However, the
> weekend commences and I'm off to my favorite free-time activity.
> 
> Tim
> 
> 
> 
> > Tim,
> > 
> > The situation with Windows is similar to what David describes
> > below. The version of GCL in your CVS does not compile (at
> > least not easily) under MinGW/Msys in Windows. But GCL 2.5
> > does.
> > 
> > The GCL developers have recently officially released 2.5.1
> > so I think it would a good idea to choose this as the
> > target GCL version for Axiom instead of the older one.
> > 
> > What do you think?
> > 
> > BTW, how goes your effort to find the bug preventing the
> > compilation of the remaining algebra modules?
> > 
> > Regards,
> > Bill.
> > 
> > > -----Original Message-----
> > > From: 
> > > address@hidden 
> > > [mailto:address@hidden
> > > .org] On Behalf Of David MENTRE
> > > Sent: Friday, March 07, 2003 2:20 PM
> > > To: address@hidden
> > > Cc: address@hidden
> > > Subject: Re: [Axiom-developer] Re: Axiom next release
> > > 
> > > 
> > > root <address@hidden> writes:
> > > 
> > > > You can't yet use the latest version of GCL. You have to use the 
> > > > version that is in the CVS archive.
> > > 
> > > Yes, I would have prefered use the version provided in your 
> > > CVS. However this version does not support the Linux/PowerPc 
> > > platform. Thus my use of the 2.5.1.
> > > 
> > > > The Common Lisp definition has changed since Axiom was written. In 
> > > > particular, use-package used to create the package if it 
> > > did not exist 
> > > > and now it does not.
> > > 
> > > But my error seems to be on a (in-package ...) S-expr. More 
> > > specifically, the first error occurs while compiling 
> > > boothdr.lisp which contains :
> > > -- boothdr.lisp --
> > > (make-package 'BOOTTRAN)
> > > (PROVIDE 'BOOTTRAN)
> > > (in-package 'BOOTTRAN :use '(LISP USER SYSTEM))
> > > -- --
> > > 
> > > If I do:
> > > -- --
> > > gcl> (compile-file "/path-to/boothdr.lisp" :output-file 
> > > gcl> "/tmp/boothdr.o")
> > > -- --
> > > it fails on (in-package ...) S-expr.
> > > 
> > > However, if I do:
> > > -- --
> > > gcl> (make-package 'BOOTTRAN)
> > > gcl> (PROVIDE 'BOOTTRAN)
> > > gcl> (compile-file "/path-to/boothdr.lisp" :output-file 
> > > gcl> "/tmp/boothdr.o")
> > > -- --
> > > it works!
> > > 
> > > I do not understand why. (sorry if it seems a dumb question, 
> > > but I'm new to (common) lisp)
> > > 
> > > 
> > > Using a trick like above in the Makefile (an echo '(progn 
> > > (make-package
> > > "boottran") ('provide "boottran") (compile-file ...) ... | 
> > > ${LISPSYS}...')), I've succeeded in compiling boothdr.lisp 
> > > but it then fails on the next .lisp file, even with the same kludge.
> > > 
> > > It seems to me that the issue is related to a non visibility 
> > > of BOOTTRAN package in the compilation environment.
> > > 
> > > > You could add another file that did nothing but a make-package for 
> > > > each of the packages you find are missing. If you pre-load 
> > > that file 
> > > > you can proceed.
> > > 
> > > Could you show me an example pattern of the lisp commands to use?
> > > 
> > > I admit my questions are newbie ones. But once again, I'm new 
> > > to common lisp.
> > > 
> > > Best regards,
> > > d.
> > > -- 
> > >  address@hidden
> > 
> > 
> 
> 
> _______________________________________________
> Axiom-developer mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/axiom-developer
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah