Re: [Gcl-devel] conditions/clos/gcl unified build patch and instructions.

[Camm Maguire]

Hi Vadim!  OK, so I take it you are hot on the trail.  Please let me
know when you get a patch version that doesn't break the maxima build,
and I'll take a look at it and commit.

1)  I'd love someone to do a quick experiment on firing up default
    gcl, creating a package, saving the image, starting the image and
    seeing the package again.  Likewise, have the package creation
    stuff in a file, compile and load the .o, save, restart, etc.

2)  This way, the "lisp" way, should certainly work.  But is there
    possibly a difference between run-time loaded objects and .o files
    linked in at compile time?  I don't think there should be, but in
    case there is, a quick approach might be to just modify the
    unixport/makefile to link in all the clcs and pcl .o files, and
    then be sure to call init_.... in unixport/sys_gcl.c

Take care,

"Vadim V. Zhytnikov" <address@hidden> writes:

> Camm Maguire ÐÉÛÅÔ:
> > Hi Vadim!  Thanks for the patch!!
> > 
> > Unfortunately, it breaks the maxima build.  As you have it, the final
> > maxima link complains that the package "COMMON-LISP-USER" does not
> > exist.  When I reverted the missing lines building this package in C,
> > the error is that package "CONDITIONS" does not exist.  Even when one
> > can fire up unixport/saved_gcl and see the conditions package.
> > 
> > Hope to look into this soon so we can commit something like the patch
> > below.
> > 
> > Take care,
> > 
> 
> It not only breaks Maxima build but in addition new loop.lisp does
> not work as expected. Try
> 
> (loop for s being the external-symbols of "COMMON-LISP" collect s)
> 
> I'm not sure but maybe the problem is that new loop.lsp (former 
> loop2.lsp in ecls) now creates extra package ANSI-LOOP
> while old loop was in SI package. In addition we probably need to
> export some symbols explicitly (loop and loop-finish as far as I 
> understand). I'm trying to understand what is going on but so far I'm
> lost in GCL compilation intricacies. I also experince problems with
> "There are no CONDITIONS ..." error and probably I've realized it's 
> origin. Having varios GCL building stages - raw_gcl, saved_gcl,
> saved_gcl (+pcl), saved_gcl (+pcl+conditions) make a lot of
> confusion.  If we compile loop.lsp with full saved_gcl+pcl+conditions 
> when some data on CONDITIONS package is saved in loop.data.
> So later when loop.data is loaded when raw_gcl makes saved_gcl
> the new image can't be created and save complains about missing CONDITIONS.
> 
> Best wishes,
> 
> Vadim
> 
> 
> 
> 
> 

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