[Gcl-devel] Re: Axiom-developer post from address@hidden requires approvalHello

[Magnus Larsson]

Hello Tim,

I checked out Axiom from CVS today around 9 pm and tried to build it using my 
i686-pc-linux-gnu, GCC-3.3.1, Binutils 2.15 system. I got the same build 
errors as before. I then performed the test as you stated them below. The 
second compile did not fail.

>
The source 
file /home/magnus/usr/source/axiom/cvs040627/axiom/int/interp/apply.clisp is 
not found.
9 
making /home/magnus/usr/source/axiom/cvs040627/axiom/mnt/linux/autoload/apply.o 
from /home/magnus/usr/source/axiom/cvs040627/axiom/obj/linux/interp/apply.o
cp: cannot stat 
`/home/magnus/usr/source/axiom/cvs040627/axiom/obj/linux/interp/apply.o': No 
such file or directory
make[3]: *** 
[/home/magnus/usr/source/axiom/cvs040627/axiom/mnt/linux/autoload/apply.o] 
Error 1
make[3]: Leaving directory 
`/home/magnus/usr/source/axiom/cvs040627/axiom/src/interp'
make[2]: *** [interpdir] Error 2
make[2]: Leaving directory `/home/magnus/usr/source/axiom/cvs040627/axiom/src'
make[1]: *** [srcdir] Error 2
make[1]: Leaving directory `/home/magnus/usr/source/axiom/cvs040627/axiom'
make: *** [all] Error 2
address@hidden:~/usr/source/axiom/cvs040627/axiom> obj/linux/bin/lisp

>(compile-file "foo.lisp")

Compiling foo.lisp.
End of Pass 1.
End of Pass 2.
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
Finished compiling foo.lisp.
#p"foo.o"

>(load "foo")

Loading foo.o
start address -T 0x83ec630 Finished loading foo.o
128

>(system::save-system "newlisp")
address@hidden:~/usr/source/axiom/cvs040627/axiom> ./newlisp

>(compile-file "foo.lisp")

Compiling foo.lisp.
End of Pass 1.
End of Pass 2.
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
Finished compiling foo.lisp.
#p"foo.o"

>(load "foo")

Loading foo.o
start address -T 0x83fff30 Finished loading foo.o
128

>(quit)
address@hidden:~/usr/source/axiom/cvs040627/axiom>

The second compile did not fail.

Magnus L

On Sunday 27 June 2004 17.32, root wrote:
> Magnus,
>
> You have the correct idea. There is just one more step...
>
> obj/linux/bin/lisp                   (start the lisp image)
> (compile-file "foo.lisp")            (compile a lisp file)
> (load "foo")                         (load the compiled file (note: no
> .lisp)) (system::save-system "newlisp")      (save a new image)
> newlisp                              (start the newimage lisp)
> (compile-file "foo.lisp")            (compile in the new image)               
>   
> (load "foo")                         (load the result)
>
>
> It is conjectured that the second compile-file will fail because
> the save-system did not build a correct image. That's what I'm
> trying to test.
>
> Tim