That was still the issue with clashes between same-named FASLs between various implementations when you're not using output-translations --- which we're not when running ASDF1 to test upgrade from it.
I've added some ASDF1 fasl deletion to run-tests.sh before the upgrade test. Will hopefully eliminate this problem.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Any sufficiently advanced incompetence is indistinguishable from malice.
On Fri, Mar 15, 2013 at 9:58 AM, Robert Goldman rpgoldman@sift.info wrote:
Works better, thanks!
Still running into an error when trying to upgrade allegromodern from 1.85, though.
What's odd is that this fails when running inside 'make test-all':
Above backtrace due to this condition: #P"/Users/rpg/lisp/asdf/build/fasls/acl-8.2m-macosx-x64/asdf/build/asdf.fasl" does not exist, cannot load Script failed upgrade FAILED for allegromodern from 1.85 using method 'load-asdf-lisp'load-asdf-system
But when I run mlisp -q and follow the directions given:
mlisp -q then copy/paste: (load"test/script-support.lisp") (asdf-test::da) (test-upgrade 'load-asdf-lisp'load-asdf-system "1.85")
everything is fine:
; Upgraded ASDF from version 1.85 to version 2.32.8 ; Registering #<system "asdf"> ;; ASDF, version 2.32.8 Testing it ;;; Installing streamc patch, version 3. ;;; Compiling file /Users/rpg/lisp/asdf/build/asdf.lisp ;;; Writing fasl file ;;; /Users/rpg/.cache/common-lisp/acl-8.2m-macosx-x64/Users/rpg/lisp/asdf/build/asdf-ASDF-TMP.fasl ;;; Fasl write complete Warning: first-feature is defined more than once as `operator' in file /Users/rpg/lisp/asdf/build/asdf.lisp. Warning: implementation-type is defined more than once as `operator' in file /Users/rpg/lisp/asdf/build/asdf.lisp. Warning: *implementation-type* is defined more than once as `variable' in file /Users/rpg/lisp/asdf/build/asdf.lisp. Warning: operating-system is defined more than once as `operator' in file /Users/rpg/lisp/asdf/build/asdf.lisp. Warning: architecture is defined more than once as `operator' in file /Users/rpg/lisp/asdf/build/asdf.lisp. ;;; Compiling file /Users/rpg/lisp/asdf/test/file1.lisp ;;; Writing fasl file ;;; /Users/rpg/.cache/common-lisp/acl-8.2m-macosx-x64/Users/rpg/lisp/asdf/test/file1-ASDF-TMP.fasl ;;; Fasl write complete ;;; Compiling file /Users/rpg/lisp/asdf/test/file2.lisp ;;; Writing fasl file ;;; /Users/rpg/.cache/common-lisp/acl-8.2m-macosx-x64/Users/rpg/lisp/asdf/test/file2-ASDF-TMP.fasl ;;; Fasl write complete ;;; Compiling file /Users/rpg/lisp/asdf/test/file3.lisp ;;; Writing fasl file ;;; /Users/rpg/.cache/common-lisp/acl-8.2m-macosx-x64/Users/rpg/lisp/asdf/test/file3-ASDF-TMP.fasl ;;; Fasl write complete ;;; Compiling file /Users/rpg/lisp/asdf/test/file4.lisp ;;; Writing fasl file ;;; /Users/rpg/.cache/common-lisp/acl-8.2m-macosx-x64/Users/rpg/lisp/asdf/test/file4-ASDF-TMP.fasl ;;; Fasl write complete Script succeeded nil
This suggests the problem may be in the testing infrastructure.
best, r
asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel