Re: Any ilisp rpm files? (w/backtrace) Almost there!

<[email protected]> Sat, 17 Aug 2002 16:46:47 -0500
Newsgroups gmane.lisp.ilisp.general
Message-ID <[email protected]>
A. F. Smith writes:
 > I did as directed with the ild file. Added .orig
 > suffux, then started up xemacs. Did m-x ->load-library
 >   ->ilisp
 > 
 > ilisp loaded. Did m-x ->cmulisp -> cmulisp loaded.
 > He's the cut/paste from it...
 > 
 > Starting lisp ...
 > CMU Common Lisp 18d, running on localhost.localdomain
 > Send questions to [email protected]. and bug reports
 > to [email protected].
 > Loaded subsystems:
 >     Python 1.0, target Intel x86
 >     CLOS based on PCL version:  September 16 92 PCL
 > (f)
 > * 
 > * ;;; Loading
 > /usr/lib/xemacs/xemacs-packages/lisp/ilisp/cl-ilisp.lisp
 > ILISP: File is not compiled, use M-x
 > ilisp-compile-inits
 > ----------------------
 > 
 > Does this mean cmucl is good to go? Is that message
 > about ILISP critical or it just an inconvenience?
 > 
 > Adam

The message about the files not being compiled is NOT critical.  It's
just an inconvenience.  If you want to make it work, restart your
emacs running as root, and do the M-x ilisp-compile-inits per their
instructions.

You are good to go however, even if you don't.

[This warning, by the way, is about uncompiled COMMON LISP files that
are used on the CL side of the ilisp interface, not about uncompiled
EMACS lisp files.]

One thing that might help track down the problem would be for you to
fire up ilisp as before.  Then, after loading ilisp, do

M-x byte-compile-file 

and when prompted for file, byte compile the ild.el file (into
ild.elc).

Then quit emacs, start up again, and M-x load-library ilisp

Let us know whether ilisp crashes again.  If it DOESN'T then whatever
makefile originally built your ild.el must be buggy and not get the
dependencies right.  If it DOES crash again as before, then there's
something wrong with the deflocal macro would be my guess.  Anyway, if
it does crash again, just remove ild.elc, and keep running without
it.  You should be fine.

cheers,
R


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390