It's not happening in a completely new checkout of the repo. I'll try to find what the difference is, though I had run svn update on the other, and svn diff showed only an inconsequential change. -Alan

On Thu, Jan 23, 2014 at 12:15 PM, Alan Ruttenberg alanruttenberg@gmail.comwrote:

I'm getting boatloads of messages of the sort:

 [java] Failed to require  CLOS because 'The function (SETF VALUES) is

undefined.' [java] ; SYSTEM:%MAKE-CONDITION triggers autoloading of org.armedbear.lisp.make_condition ... [java] ; Autoloaded org.armedbear.lisp.make_condition (0.0030 seconds) [java] Failed to require PRINT-OBJECT because 'Don't know how to REQUIRE CLOS.' [java] ; COMMON-LISP:INVOKE-DEBUGGER triggers autoloading of debug ... [java] ; Autoloaded debug (0.013 seconds) [java] ; COMMON-LISP:FRESH-LINE triggers autoloading of pprint ... [java] ; Loading /Users/alanr/repos/abcl/src/org/armedbear/lisp/print.lisp ... [java] ; Loaded /Users/alanr/repos/abcl/src/org/armedbear/lisp/print.lisp (0.053 seconds) [java] ; Loading /Users/alanr/repos/abcl/src/org/armedbear/lisp/print-object.lisp ... [java] ; Loading /Users/alanr/repos/abcl/src/org/armedbear/lisp/clos.lisp ... [java] Failed to require CLOS because 'The function (SETF VALUES) is undefined.' [java] Failed to require PRINT-OBJECT because 'Don't know how to REQUIRE CLOS.'