Re: Help.doc loading in Binary
Daniel Kochmański <[email protected]>
| Newsgroups | gmane.lisp.ecl.general |
|---|---|
| Message-ID | <[email protected]> |
Hey, here is a patch which will probably work for you (not tested): -- cut here-- diff --git a/src/lsp/helpfile.lsp b/src/lsp/helpfile.lsp index 09c7cb32..62e6985a 100644 --- a/src/lsp/helpfile.lsp +++ b/src/lsp/helpfile.lsp @@ -18,18 +18,18 @@ ;;;; Documentation system ;;;; -#+ecl-min +;#+ecl-min (progn (*make-special '*documentation-pool*) (setq *documentation-pool* nil) (*make-special '*keep-documentation*) (setq *keep-documentation* t)) -#-ecl-min -(progn - (setq *documentation-pool* - (list (make-hash-table :test #'equal :size 128) - "SYS:help.doc")) - (defparameter *keep-documentation* t)) +;; #-ecl-min +;; (progn +;; (setq *documentation-pool* +;; (list (make-hash-table :test #'equal :size 128) +;; "SYS:help.doc")) +;; (defparameter *keep-documentation* t)) (defun new-documentation-pool (&optional (size 1024)) "Args: (&optional hash-size) --cut here-- regards, Daniel On 05.10.2017 05:29, John Mercouris wrote: > Hello everyone, I’m running ECL + EQL 16.1.3, Mac OS High Sierra > > I can produce a binary with ECL, but I have an issue, when I try to run it on anybody’s computer: I get the following: > > ------------------------------------------------------ > > Condition of type: FILE-ERROR > Filesystem error with pathname “SYS:help.doc”. > Either > 1) the file does not exist, or > 2) we are not allowed to access the file, or > 3) the pathname points to a broken symbolic link. > No restarts available. > > Top level in: #<process TOP-LEVEL>. > ------------------------------------------------------ > > I’ve determined that the cause of this error is a file missing at: /usr/local/lib/ecl-16.1.3/help.doc > > I’ve been able to get binary files to work on other people’s machines by copying the help.doc file to the appropriate > dir. Unfortunately this is not a practical solution for distribution. > > Is there any way to tell ECL to not attempt to load this file? Any patch I can apply to the source? Thanks, > > -John