0.7.4.20:

	workaround for openmcl 0.11 as xc host (the openmcl bug CSR
		noted as "Extra superclass in FILE-ERROR", I presume)

diff --git a/src/code/error.lisp b/src/code/error.lisp
index 1239eb4..56ce2ac 100644 (file)
--- a/src/code/error.lisp
+++ b/src/code/error.lisp
@@ -46,6 +46,11 @@
              (case-failure-possibilities condition)))))
 
 (define-condition simple-control-error (simple-condition control-error) ())
+;;; OpenMCL 0.11 can't compile this, so just skip it, since it
+;;; shouldn't be needed on the happy path anyway. FIXME: CSR says
+;;; that 0.12 should be able to compile this, so this #- should
+;;; be removable real soon now.
+#-(and openmcl sb-xc-host)
 (define-condition simple-file-error    (simple-condition file-error)    ())
 (define-condition simple-program-error (simple-condition program-error) ())
 (define-condition simple-stream-error  (simple-condition stream-error)  ())

diff --git a/src/compiler/early-c.lisp b/src/compiler/early-c.lisp
index ce5199b..e2c677a 100644 (file)
--- a/src/compiler/early-c.lisp
+++ b/src/compiler/early-c.lisp
@@ -160,8 +160,8 @@
     ;;         (FOO 14)))
     ;; and then we happen to compile bar.lisp before foo.lisp.
   (when (looks-like-name-of-special-var-p symbol)
-      ;; FIXME: should be COMPILER-STYLE-WARNING?
-      (style-warn "using the lexical binding of the symbol ~S, not the~@
+    ;; FIXME: should be COMPILER-STYLE-WARNING?
+    (style-warn "using the lexical binding of the symbol ~S, not the~@
 dynamic binding, even though the symbol name follows the usual naming~@
 convention (names like *FOO*) for special variables" symbol))
   (values))