Re: Compiling Maxima with GCL 2.7.2 pre-release results in empty executable

David Scherfgen via Maxima-discuss <[email protected]>
Newsgroups gmane.comp.mathematics.maxima.general,gmane.lisp.gcl.devel
Message-ID <CAMTHLKjvExEorSgyz_oZM09aQJhn0YMvQ-=PPO7DAesD7U91Zg@mail.gmail.com>
Hi Robert,

I tried the same thing today, with success, using the normal sequence of
commands: ./bootstrap, ./configure --enable-gcl and make, then I ran
./maxima-local and ran the test suite. 2 tests passed that were expected to
fail, no unexpected failures.
I used the GCL 2.7.1-17 pre-release branch.

Best regards
David

Am Di., 14. Apr. 2026 um 21:41 Uhr schrieb Robert Dodier <
[email protected]>:

> I built GCL from the 2.7.2 pre-release branch and that was apparently
> successful.
>
> I compiled current Maxima from Git with that GCL, and although the
> process was apparently successful, it resulted in a maxima executable
> that had only a few Maxima symbols in it -- stuff related to autoconf
> variables and the like.
>
> I noticed it because CL-USER::RUN was missing, but that's just one of
> many items; almost everything is missing.
>
> To be precise, I did something like
>
> (do-symbols (s (find-package "MAXIMA"))
>   (if (equalp (symbol-package s) (find-package "MAXIMA")) (print s)))
>
> Maybe the Maxima symbols ended up in some other package? I didn't try
> to figure it out.
>
> If anyone has any ideas what's going on, I would be interested to hear.
>
> Robert
>
>
> _______________________________________________
> Maxima-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/maxima-discuss
>

_______________________________________________
Maxima-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maxima-discuss
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.