femlisp-user
[Top][All Lists]
Advanced

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

Re: [femlisp-user] getting errors on SuSE8.2


From: Nicolas Neuss
Subject: Re: [femlisp-user] getting errors on SuSE8.2
Date: 15 Dec 2003 10:06:50 +0100
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

osman buyuk <address@hidden> writes:

> Hi,
>   I had femlisp working on my suse7.x system. Now updated to 8.2  and updated 
> gcc to 3.3.2 full release, but getting the following errors:
> 
> ....
> 
> Shows the regular refinement of a triangle.
> 
> Error in function UNIX::SIGPIPE-HANDLER:  SIGPIPE at #x401243A8.
>    [Condition of type SIMPLE-ERROR]
> 
> Restarts:
>   0: [ABORT] Return to Top-Level.
> 
> Debug  (type H for help)
> 
> (UNIX::SIGPIPE-HANDLER #<#1=unused-arg> #<#1#> #.(SYSTEM:INT-SAP #x3FFFC7E0))
> Source: Error finding source:
> Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM:  Source file no longer 
> exists:
>   target:code/signal.lisp.
> 
> any ideas?
> 
> TIA
> osman

Does OpenDX work using the command "dx" from the shell on which femlisp is
started?  The configuration of the DX via shell variables is not yet
correctly taken into account in the current Femlisp version.  A patch in
"femlisp:src;femlisp-config.lisp" should look about as follows:

(defparameter *dx-path*
  (or
   #+cmu (let ((string (cdr (assoc :OPENDX_BINARY ext:*environment-list*))))
           (when string
             (probe-file (pathname string))))
   (probe-file (pathname "path:dx")))
  "The path to the Data Explorer executable.")

Then you can set the environment variable OPENDX_BINARY in the shell where
Femlisp is started.  (Alternatively, you could set *dx-path* in
"femlisp:src;femlisp-config.lisp" to whatever you want.)

If this does not help: What does backtrace say (type "backtrace" or "ba" at
the debugger prompt)?

Nicolas.





reply via email to

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