|
From: Thomas D. D. <to...@sp...> - 2017-06-26 20:07:13
|
On 06/25/2017 10:12 PM, Gunter Königsmann wrote: > In other words: There are gcl installs that work fine and others > (perhaps due to a bugfix in gcl that didn't affect the version number, > there seem to have been at least 53 of these.) that fail to compile > maxima if a few directories and sys-proclaim.lisp are missing (or that > randomly fail and happen to succeed every time I manually create these > items. But in this case it would be interesting to know what makes even > single-process-builds non-deterministic. > Have I been talking at cross purposes?? I have been addressing building maxima with gcl re GCL: ======================================== I use GCL 2.6.12 from the release tarball, gcl-2.6.12.tar.gz. Building GCL from the release tarball works. I use: ./configure --enable-ansi --enable-readline I think the GNU GCL build from git head has been broken for some time. I searched, seems there is no bug report on this. I submitted one. re MAXIMA: ====================================== As far as I can tell, the IN SOURCE TREE building maxima with the 2.6.12 GCL release always succeeds. The out of source tree maxima with the same GCL build always fails. Tom Dean |