Re: Building with gcl recompiles everything?

On 4/10/26 6:54 AM, Leo Butler wrote:

> On Thu, Apr 09 2026, Raymond Toy<[email protected]> wrote:
>
>> On 4/9/26 8:33 AM, Leo Butler wrote:
>>
>>> On Mon, Apr 06 2026, Raymond Toy<[email protected]> wrote:
>>>
>> None of this is relevant, though, to gcl recompiling the world when
>> only one independent file is changed.
> If the gcl compiler were as fast as it was 10 years ago, the problem you
> mention would not be so vexing.
I haven’t done an incremental compile with gcl in ages.
> My experience is that, if I try some incremental changes and re-compile
> the build, the gcl build is always broken (this has been true for as
> long as I can remember). My only recourse is to nuke src/binary-gcl and
> rebuild from scratch. That is why I bring up the slow compiler.

I’m pretty sure the dependencies in maxima.system are not fully correct. 
That could explain the brokenness. It’s not easy to fix because you need 
a call tree of who calls what and then update all the dependencies. And 
it’s possible some dependencies are circular. I suppose this is 
something an AI would be good at.

I’ll try to look into why gcl incremental compiles aren’t. Hopefully, 
it’s a simple oversight in defsystem or a simple bug in timestamps.

&#8203;

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