axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Axiom-developer] Problems building wh-sandbox


From: Mike Hansen
Subject: [Axiom-developer] Problems building wh-sandbox
Date: Wed, 6 Jun 2007 04:44:48 -0700

Hello,
I'm trying to build the wh-sandbox tree, but get the following error
when running 'make'.  I'm not familiar enough with the build process
and LISP to effectively figure out the problem.  Here is the error:

echo '(compiler::link (quote ("axiom-package.lisp" "axiom-lisp.o")) "lisp" ' \
             ' (format nil "(progn (let ((*load-path* (cons ~S *load-path*))'\
                                       ' (si::*load-types* ~S))' \
                                      ' (compiler::emit-fn t))' \
                                 ' (when (fboundp (quote si::sgc-on))' \
                                       ' (si::sgc-on t))' \
                                 ' (setq compiler::*default-system-p* t))"' \
                     ' si::*system-directory* (quote (list ".lsp")))' \
              '
"/opt/axiom/wh-build/src/lisp/../.././src/lib/bsdsignal.o
/opt/axiom/wh-build/src/lisp/../.././src/lib/cfuns-c.o
/opt/axiom/wh-build/src/lisp/../.././src/lib/sockio-c.o  -lutil")' \
           | /usr/bin/gcl
GCL (GNU Common Lisp)  2.6.7 CLtL1    Nov 10 2006 14:25:02
Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
Binary License:  GPL due to GPL'ed components: (XGCL READLINE BFD 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/

GCL (GNU Common Lisp)  April 1994  262144 pages
Building symbol table for /opt/axiom/wh-build/src/lisp/raw_lisp ..
I'm not an object
Lisp initialization failed.

"lisp"

/usr/bin/install -c lisp /opt/axiom/wh-build/build/x86_64-unknown-linux/bin
/usr/bin/install: cannot stat `lisp': No such file or directory
make: *** [do_it.gcl] Error 1


How would I go about fixing this?

Thanks,
Mike




reply via email to

[Prev in Thread] Current Thread [Next in Thread]