Re: [Matlisp-users] Terminating Makefile

[Nicolas N. <Nic...@iw...>]

Raymond Toy <to...@rt...> writes:

> >>>>> "Nicolas" == Nicolas Neuss <Nic...@iw...> writes:
> 
>     Nicolas> For my Femlisp installation shell script I cannot build Matlisp via
>     Nicolas> configure/make, because the Makefile remains hanging in CMUCL until the
>     Nicolas> user types (quit).
> 
> [snip]
> 
>     Nicolas> This is not optimal, so that I suggest to change matlisp.mk.in as follows:
> 
>     Nicolas> all : $(MATLIB) lib/lazy-loader.o
>     Nicolas> 	$(LISPEXEC) $(LISPEVAL) '(progn (load "start.lisp"))'
> 
>     Nicolas> becomes
> 
>     Nicolas> all : $(MATLIB) lib/lazy-loader.o
>     Nicolas> 	$(LISPEXEC) $(LISPEVAL) '(progn (load "start.lisp") (ext:quit))'
> 
>     Nicolas> What do you think?
> 
> This is acceptable to me.  However, I think we need to think about
> adding a script or something for the user to run to do the necessary
> magic to get him into matlisp.  We may also want to create a
> matlisp.core, which I don't think currently happens.  But I tend not
> to save cores and instead load up the individual fasls.  But matlisp
> is big so loading these is a bit slow....
> 
> Ray

You could do (for CMUCL, I don't know ACL) something like:

all : $(MATLIB) lib/lazy-loader.o
        $(LISPEXEC) -eval "(ext:save-lisp \"matlisp\" :print-herald t)" -eval "(quit)"

BTW: does this work on all platforms?  Recently, I observed that my
restarted core did not find "dcopy_" anymore.  On the other hand, I
remember having saved CMUCL/Matlisp successfully before.

Nicolas.