Re: Building with gcl recompiles everything?

On 4/6/26 7:09 PM, Raymond Toy wrote:

> Has any one noticed that if you change one file, like cl-info.lisp and 
> you run make again, gcl ends up compiling the world. Other lisps just 
> compile up cl-info and a few others that depend on it.
>
> This is rather annoying because it takes a very long time to compile 
> maxima from scratch with gcl on my machine.
>
> Are the dependencies or time-stamps for the fasls somehow broken on gcl?
>
I suspect it has to do with tools/sys-proclaim.lisp. The Makefile has a 
rule for gcl that removes binary-gcl directory (twice).

I have a vague memory that sys-proclaim used to be checked in but was 
always out-of-date because no one bothered to update it. At some point 
it was not checked in and was autogenerated. Perhaps when gcl compiled 
faster, it wasn’t a problem. But now that it’s really slow, it is a 
headache.

I also have a vague memory that sys-proclaim was supposed to be updated 
only if things actually changed but I might be wrong about that.

To generate a sys-proclaim file, I think you need to compile the world 
to get all the functions defined.

I don’t remember how any of this stuff worked.

Perhaps Camm can provide some insight?

​

_______________________________________________
Maxima-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maxima-discuss