[Axiom-developer] open-axiom-1.4.2 cannot be built with sbcl-1.1.18

2014-05-18 Thread daly
Helmut, This problem is not related to Axiom. They are different projects. Please do not copy axiom-developer@nongnu.org on your mailings. Thank you. Tim Daly ___ Axiom-developer mailing list Axiom-developer@nongnu.org https://lists.nongnu.org/mailma

Re: [Axiom-developer] open-axiom-1.4.2 cannot be built with sbcl-1.1.18

2014-05-18 Thread Gabriel Dos Reis
On Tue, May 13, 2014 at 4:32 AM, Helmut Jarausch < jarau...@igpm.rwth-aachen.de> wrote: > > > I have built Fricas and Maxima successfully with SBCL. > > What is so special about Open-Axiom? > > Of course, no source program should ever get a compiler in producing > memory faults. But is it only SBC

Re: [Axiom-developer] open-axiom-1.4.2 cannot be built with sbcl-1.1.18

2014-05-18 Thread Gabriel Dos Reis
On Tue, May 13, 2014 at 4:32 AM, Helmut Jarausch < jarau...@igpm.rwth-aachen.de> wrote: > Hi, > > I'm trying to build open-axiom-1.4.2 with SBCL-1.1.18. > It fails with strange memory errors like > > ; compiling (DEFUN |bfOR| ...) > ; compiling (DEFUN |bfAND| ...)CORRUPTION WARNING in SBCL pid 922

[Axiom-developer] open-axiom-1.4.2 cannot be built with sbcl-1.1.18

2014-05-13 Thread daly
Helmut, You have the wrong mailing list. The names of the two projects is a source of confusion. This is the mailing list for Axiom. Please contact Gaby. Tim Daly ___ Axiom-developer mailing list Axiom-developer@nongnu.org https://lists.nongnu.org/mai

[Axiom-developer] open-axiom-1.4.2 cannot be built with sbcl-1.1.18

2014-05-13 Thread Helmut Jarausch
Hi, I'm trying to build open-axiom-1.4.2 with SBCL-1.1.18. It fails with strange memory errors like ; compiling (DEFUN |bfOR| ...) ; compiling (DEFUN |bfAND| ...)CORRUPTION WARNING in SBCL pid 9224(tid 140737353516800): Memory fault at 1878002f (pc=0x100099ca66, sp=0x76c8eaf8) The integri

[Axiom-developer] open-axiom-1.4.2 cannot be built with sbcl-1.1.18

2014-05-13 Thread daly
Helmut, Please contact Gabriel Dos Reis, copied above, for help. The SBCL problem is not unusual. One of the hard parts of a large project is the amount of time spent keeping up with the many different ports to many platforms. You might consider trying it on a prior version of SBCL to see if y