I built gcl manually per suggestion. Based on suggestions
I used the following configure command:

./configure --prefix=/usr/local \
--enable-vssize=65536*2 --enable-maxpage=256*1024 \
--disable-x --disable-xgcl --disable-tkconfig

After installing gcl, I configured Axiom:
./configure --with-gcl

During make, I have problem with bootsys:
make[2]: Entering directory 
`/home/harke/Axiom-svn/build-improvements/src/boot'
Building stage 1
[ -d stage1 ] || ../../config/mkinstalldirs stage1
make OBJECTS="boothdr.o exports.o npextras.o ptyout.o btincl2.o btscan2.o 
typrops.o btpile2.o typars.o tyextra.o tytree1.o" bootsys
make[3]: Entering directory 
`/home/harke/Axiom-svn/build-improvements/src/boot'
echo '(boottran::boottocl "ptyout.boot")' | prev-stage/bootsys
GCL (GNU Common Lisp)  2.6.8 CLtL1    Nov  8 2006 19:12:07
Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
Binary License:  GPL due to GPL'ed components: (UNEXEC)
Modifications of this banner must retain notice of a compatible license
Dedicated to the memory of W. Schelter

Use (help) to get some basic information on how to use GCL.
Temporary directory for compiler files set to /tmp/

>
Error: Caught fatal error [memory may be damaged]
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by EVAL.
Broken at BOOTTRAN:BOOTTOCL.  Type :H for Help.
>>make[3]: *** [ptyout.clisp] Error 255
make[3]: Leaving directory `/home/harke/Axiom-svn/build-improvements/src/boot'
make[2]: *** [stage1/bootsys] Error 2
make[2]: Leaving directory `/home/harke/Axiom-svn/build-improvements/src/boot'
make[1]: *** [boot/stamp] Error 2
make[1]: Leaving directory `/home/harke/Axiom-svn/build-improvements/src'
make: *** [all-recursive] Error 1

I have been doing a make clean between attempts but I think
some file times don't reflect this. I tried make dist-clean but
didn't work. What is the best way to reset?

Richard


_______________________________________________
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer

Reply via email to