Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial startup fails on Catalina with SBCL #54

Open
GlenHenshaw opened this issue Dec 17, 2019 · 2 comments
Open

Initial startup fails on Catalina with SBCL #54

GlenHenshaw opened this issue Dec 17, 2019 · 2 comments

Comments

@GlenHenshaw
Copy link

$ sbcl --load ./cl-jupyter.lisp
This is SBCL 1.5.9, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
... initialization mode... please wait...
To load "cl-jupyter":
  Load 1 ASDF system:
    cl-jupyter
; Loading "cl-jupyter"
...While evaluating the form starting at line 5, column 0
  of #P"/Users/glenhenshaw/Code/cl-jupyter/./cl-jupyter.lisp":

debugger invoked on a ASDF/SESSION:FORMATTED-SYSTEM-DEFINITION-ERROR in thread
#<THREAD "main thread" RUNNING {10005184C3}>:
  OPERATION instances must only be created through MAKE-OPERATION.

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [RETRY                        ] Retry
                                     compiling #<GROVEL-FILE "pzmq" "grovel">.
  1: [ACCEPT                       ] Continue, treating
                                     compiling #<GROVEL-FILE "pzmq" "grovel">
                                     as having been successful.
  2:                                 Retry ASDF operation.
  3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
                                     configuration.
  4:                                 Retry ASDF operation.
  5:                                 Retry ASDF operation after resetting the
                                     configuration.
  6: [ABORT                        ] Give up on "cl-jupyter"
  7: [RETRY                        ] Retry EVAL of current toplevel form.
  8: [CONTINUE                     ] Ignore error and continue loading file "/Users/glenhenshaw/Code/cl-jupyter/./cl-jupyter.lisp".
  9:                                 Abort loading file "/Users/glenhenshaw/Code/cl-jupyter/./cl-jupyter.lisp".
 10:                                 Ignore runtime option --load "./cl-jupyter.lisp".
 11:                                 Skip rest of --eval and --load options.
 12:                                 Skip to toplevel READ/EVAL/PRINT loop.
 13: [EXIT                         ] Exit SBCL (calling #'EXIT, killing the process).

(ASDF/SESSION:SYSDEF-ERROR "OPERATION instances must only be created through MAKE-OPERATION.")
   source: (ERROR 'FORMATTED-SYSTEM-DEFINITION-ERROR :FORMAT-CONTROL FORMAT
                  :FORMAT-ARGUMENTS ARGUMENTS)
0] 
@fredokun
Copy link
Owner

Since it's the last version of sbcl there may be some incompatible dependency ? The error seems related to ASDF (and maybe quicklisp ?). I'll try to reproduce it anyways.

@GlenHenshaw
Copy link
Author

GlenHenshaw commented Dec 17, 2019

...I think this is probably pilot error. Uninstalling sbcl via Homebrew, followed by deleting the quicklisp directory and installing everything from scratch, appears to mostly have solved the problem.

The one remaining problem was an error when starting the Jupyter lisp kernel that reported that "sbcl" cannot be found. Homebrew installs into /usr/local/bin, and it looks like Jupyter isn't looking there. So I modified the json file directly to give it an absolute path to sbcl and then it started working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants