On 6/24/10 11:51 PM, Faré wrote:
Can ABCL upgrade its ASDF to 2.003 or whichever is latest in the
release branch (if possible NOT the master branch)?
That would be great. It should fix several bugs that may have hit ABCL
users since then. Xach at least reported that upgrading ASDF on ABCL
made his software work.
As usual, please test on your specific implementation with a few
systems before you commit, and please report any bug.
Committed in [ABCL svn r12765][1].
Attached are the ABCL specific modifications to asdf-2.003, namely
differentiation of the output locations by ABCL FASL version and the
Java platform we're running under.
[1]: http://trac.common-lisp.net/armedbear/changeset/12765
--
"A screaming comes across the sky. It has happened before, but there
is nothing to compare to it now."
--- /Users/evenson/work/asdf/asdf.lisp 2010-06-25 09:12:46.000000000 +0200
+++ src/org/armedbear/lisp/asdf.lisp 2010-06-25 09:39:38.000000000 +0200
@@ -2392,7 +2392,8 @@
(defparameter *architecture-features*
'((:x86-64 :amd64 :x86_64 :x8664-target)
(:x86 :i686 :i586 :pentium3 :i486 :i386 :pc386 :iapx386 :x8632-target :pentium4)
- :hppa64 :hppa :ppc64 (:ppc32 :ppc :powerpc) :sparc64 :sparc))
+ :hppa64 :hppa :ppc64 (:ppc32 :ppc :powerpc) :sparc64 :sparc
+ :java-1.4 :java-1.5 :java-1.6 :java-1.7))
(defun lisp-version-string ()
(let ((s (lisp-implementation-version)))
@@ -2424,7 +2425,8 @@
#+lispworks (format nil "~...@[~a~]" s
(when (member :lispworks-64bit *features*) "-64bit"))
;; #+sbcl (format nil "~a-fasl~d" s sb-fasl:+fasl-file-version+) ; fasl-f-v is redundant
- #+(or armedbear cormanlisp mcl sbcl scl) s
+ #+armedbear (format nil "~a-fasl~a" s system::*fasl-version*)
+ #+(or cormanlisp mcl sbcl scl) s
#-(or allegro armedbear clisp clozure cmu cormanlisp digitool
ecl gcl lispworks mcl sbcl scl) s))
_______________________________________________
asdf-devel mailing list
[email protected]
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
