- asdf-devel - mailman3.common-lisp.net

Re: [asdf-devel] SBCL failure on test-configuration.script with latest ASDF
by Robert Goldman 09 Nov '11

09 Nov '11

On 11/8/11 Nov 8 -11:27 AM, Zach Beane wrote: > Robert Goldman <rpgoldman(a)sift.info> writes: > >> I tested the latest ASDF from git with SBCL 1.0.47, and got the >> following test failure in test-configuration.script. Upgraded to SBCL >> head (SBCL 1.0.53.1-6b0e405) and I still get this test failure. >> >> Mac OS X, 64-bit, threading enabled (don't see why that would make a >> difference, but...). > > I'm not sure I see the test failure.… [View More] Was it meant to be attached? > > Zach Yes, it was. Here I will try again (I wonder if this is related to recent symlinks changes; looks like ASDF is misinterpreting a file as a subdirectory): + sbcl --noinform --userinit /dev/null --sysinit /dev/null --disable-debugger --eval '(load "test-configuration.script")' subdirectories of dir2/: (#P"/Users/rpg/lisp/asdf/tmp/dir2/dir3/" #P"/Users/rpg/lisp/asdf/tmp/dir2/dir4/" #P"/Users/rpg/lisp/asdf/tmp/dir2/foo3.asd") The assertion (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/")))) failed. ABORTING: #<SIMPLE-ERROR "The assertion ~S failed." {1002EA3A03}> 0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {1002EA5A6B}> :START 0 :COUNT 69) 1: (SB-DEBUG:BACKTRACE 69 #<SYNONYM-STREAM :SYMBOL *TERMINAL-IO* {10001E4613}>) 2: ((FLET #:LAMBDA0) #<SIMPLE-ERROR "The assertion ~S failed." {1002EA3A03}>) 3: (SIGNAL #<SIMPLE-ERROR "The assertion ~S failed." {1002EA3A03}>) 4: (ERROR #<SIMPLE-ERROR "The assertion ~S failed." {1002EA3A03}>) 5: (SB-KERNEL:ASSERT-ERROR (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/")))) NIL NIL) 6: ((LAMBDA ())) 7: (COMMON-LISP-USER::CALL-QUITTING-ON-ERROR #<FUNCTION (LAMBDA #) {1002E1C49B}>) 8: (SB-INT:SIMPLE-EVAL-IN-LEXENV (COMMON-LISP-USER::QUIT-ON-ERROR (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/foo:/bar::/baz:/quux") '(:OUTPUT-TRANSLATIONS ("/foo" "/bar") :INHERIT-CONFIGURATION ("/baz" "/quux")))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/:") '(:OUTPUT-TRANSLATIONS ("/" NIL) :IGNORE-INHERITED-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/::") '(:OUTPUT-TRANSLATIONS ("/" NIL) :INHERIT-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/:/") '(:OUTPUT-TRANSLATIONS ("/" "/") :IGNORE-INHERITED-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "(:output-translations (\"/\" \"/\") :ignore-inherited-configuration)") '(:OUTPUT-TRANSLATIONS ("/" "/") :IGNORE-INHERITED-CONFIGURATION))) (CREATE-ASD-FILES) (CREATE-CONF-FILES) (FORMAT T "~&subdirectories of dir2/: ~S~%" (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/"))) (ASSERT (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/"))))) (FORMAT T "~&subdirectories of dir5/: ~S~%" (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir5/"))) (ASSERT (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir5/"))))) (INITIALIZE-SOURCE-REGISTRY `(:SOURCE-REGISTRY (:INCLUDE ,(UNDER-TEST-DIRECTORY "conf.d/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir5/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir8/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir9/dira/")) :IGNORE-INHERITED-CONFIGURATION)) (FORMAT T "~&Source Registry: ~S~%" *SOURCE-REGISTRY*) (ASSERT (FIND-SYSTEM :FOO0 NIL)) (ASSERT (FIND-SYSTEM :FOO1 NIL)) (ASSERT (FIND-SYSTEM :FOO2 NIL)) (ASSERT (FIND-SYSTEM :FOO3 NIL)) (ASSERT (FIND-SYSTEM :FOO4 NIL)) (ASSERT (NOT (FIND-SYSTEM :FOO5 NIL))) (ASSERT (FIND-SYSTEM :FOO6 NIL)) (ASSERT (FIND-SYSTEM :FOO7 NIL)) (ASSERT (FIND-SYSTEM :FOO8 NIL)) (ASSERT (NOT (FIND-SYSTEM :FOO9 NIL))) (FORMAT T "~&A: ~S~%B: ~S~%" (NAMESTRING (SYSTEM-RELATIVE-PATHNAME :FOO3 "bar/baz.lisp")) (UNDER-TEST-DIRECTORY "dir2/bar/baz.lisp")) (ASSERT (EQUAL (NAMESTRING (SYSTEM-RELATIVE-PATHNAME :FOO3 "bar/baz.lisp")) (UNDER-TEST-DIRECTORY "dir2/bar/baz.lisp")))) #<NULL-LEXENV>) 9: (SB-EXT:EVAL-TLF (COMMON-LISP-USER::QUIT-ON-ERROR (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/foo:/bar::/baz:/quux") '(:OUTPUT-TRANSLATIONS ("/foo" "/bar") :INHERIT-CONFIGURATION ("/baz" "/quux")))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/:") '(:OUTPUT-TRANSLATIONS ("/" NIL) :IGNORE-INHERITED-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/::") '(:OUTPUT-TRANSLATIONS ("/" NIL) :INHERIT-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/:/") '(:OUTPUT-TRANSLATIONS ("/" "/") :IGNORE-INHERITED-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "(:output-translations (\"/\" \"/\") :ignore-inherited-configuration)") '(:OUTPUT-TRANSLATIONS ("/" "/") :IGNORE-INHERITED-CONFIGURATION))) (CREATE-ASD-FILES) (CREATE-CONF-FILES) (FORMAT T "~&subdirectories of dir2/: ~S~%" (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/"))) (ASSERT (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/"))))) (FORMAT T "~&subdirectories of dir5/: ~S~%" (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir5/"))) (ASSERT (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir5/"))))) (INITIALIZE-SOURCE-REGISTRY `(:SOURCE-REGISTRY (:INCLUDE ,(UNDER-TEST-DIRECTORY "conf.d/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir5/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir8/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir9/dira/")) :IGNORE-INHERITED-CONFIGURATION)) (FORMAT T "~&Source Registry: ~S~%" *SOURCE-REGISTRY*) (ASSERT (FIND-SYSTEM :FOO0 NIL)) (ASSERT (FIND-SYSTEM :FOO1 NIL)) (ASSERT (FIND-SYSTEM :FOO2 NIL)) (ASSERT (FIND-SYSTEM :FOO3 NIL)) (ASSERT (FIND-SYSTEM :FOO4 NIL)) (ASSERT (NOT (FIND-SYSTEM :FOO5 NIL))) (ASSERT (FIND-SYSTEM :FOO6 NIL)) (ASSERT (FIND-SYSTEM :FOO7 NIL)) (ASSERT (FIND-SYSTEM :FOO8 NIL)) (ASSERT (NOT (FIND-SYSTEM :FOO9 NIL))) (FORMAT T "~&A: ~S~%B: ~S~%" (NAMESTRING (SYSTEM-RELATIVE-PATHNAME :FOO3 "bar/baz.lisp")) (UNDER-TEST-DIRECTORY "dir2/bar/baz.lisp")) (ASSERT (EQUAL (NAMESTRING (SYSTEM-RELATIVE-PATHNAME :FOO3 "bar/baz.lisp")) (UNDER-TEST-DIRECTORY "dir2/bar/baz.lisp")))) 8 #<NULL-LEXENV>) 10: ((FLET SB-FASL::EVAL-FORM) (COMMON-LISP-USER::QUIT-ON-ERROR (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/foo:/bar::/baz:/quux") '(:OUTPUT-TRANSLATIONS ("/foo" "/bar") :INHERIT-CONFIGURATION ("/baz" "/quux")))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/:") '(:OUTPUT-TRANSLATIONS ("/" NIL) :IGNORE-INHERITED-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/::") '(:OUTPUT-TRANSLATIONS ("/" NIL) :INHERIT-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "/:/") '(:OUTPUT-TRANSLATIONS ("/" "/") :IGNORE-INHERITED-CONFIGURATION))) (ASSERT (EQUAL (PARSE-OUTPUT-TRANSLATIONS-STRING "(:output-translations (\"/\" \"/\") :ignore-inherited-configuration)") '(:OUTPUT-TRANSLATIONS ("/" "/") :IGNORE-INHERITED-CONFIGURATION))) (CREATE-ASD-FILES) (CREATE-CONF-FILES) (FORMAT T "~&subdirectories of dir2/: ~S~%" (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/"))) (ASSERT (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir2/"))))) (FORMAT T "~&subdirectories of dir5/: ~S~%" (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir5/"))) (ASSERT (= 2 (LENGTH (SUBDIRECTORIES (UNDER-TEST-DIRECTORY "dir5/"))))) (INITIALIZE-SOURCE-REGISTRY `(:SOURCE-REGISTRY (:INCLUDE ,(UNDER-TEST-DIRECTORY "conf.d/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir5/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir8/")) (:INCLUDE ,(UNDER-TEST-DIRECTORY "dir9/dira/")) :IGNORE-INHERITED-CONFIGURATION)) (FORMAT T "~&Source Registry: ~S~%" *SOURCE-REGISTRY*) (ASSERT (FIND-SYSTEM :FOO0 NIL)) (ASSERT (FIND-SYSTEM :FOO1 NIL)) (ASSERT (FIND-SYSTEM :FOO2 NIL)) (ASSERT (FIND-SYSTEM :FOO3 NIL)) (ASSERT (FIND-SYSTEM :FOO4 NIL)) (ASSERT (NOT (FIND-SYSTEM :FOO5 NIL))) (ASSERT (FIND-SYSTEM :FOO6 NIL)) (ASSERT (FIND-SYSTEM :FOO7 NIL)) (ASSERT (FIND-SYSTEM :FOO8 NIL)) (ASSERT (NOT (FIND-SYSTEM :FOO9 NIL))) (FORMAT T "~&A: ~S~%B: ~S~%" (NAMESTRING (SYSTEM-RELATIVE-PATHNAME :FOO3 "bar/baz.lisp")) (UNDER-TEST-DIRECTORY "dir2/bar/baz.lisp")) (ASSERT (EQUAL (NAMESTRING (SYSTEM-RELATIVE-PATHNAME :FOO3 "bar/baz.lisp")) (UNDER-TEST-DIRECTORY "dir2/bar/baz.lisp")))) 8) 11: (SB-INT:LOAD-AS-SOURCE #<SB-SYS:FD-STREAM for "file /Users/rpg/lisp/asdf/test/test-configuration.script" {10029358E3}> :VERBOSE NIL :PRINT NIL :CONTEXT "loading") 12: ((FLET SB-FASL::LOAD-STREAM) #<SB-SYS:FD-STREAM for "file /Users/rpg/lisp/asdf/test/test-configuration.script" {10029358E3}> NIL) 13: (LOAD "test-configuration.script" :VERBOSE NIL :PRINT NIL :IF-DOES-NOT-EXIST T :EXTERNAL-FORMAT :DEFAULT) 14: (SB-INT:SIMPLE-EVAL-IN-LEXENV (LOAD "test-configuration.script") #<NULL-LEXENV>) 15: (EVAL (LOAD "test-configuration.script")) 16: (SB-IMPL::PROCESS-EVAL/LOAD-OPTIONS ((:EVAL . "(load \"test-configuration.script\")"))) 17: (SB-IMPL::TOPLEVEL-INIT) 18: ((FLET #:WITHOUT-INTERRUPTS-BODY-[RESTART-LISP]38)) 19: ((LABELS SB-IMPL::RESTART-LISP)) ABORTING: #<SIMPLE-ERROR "The assertion ~S failed." {1002EA3A03}> Script failed Using sbcl --noinform --userinit /dev/null --sysinit /dev/null --disable-debugger, test-configuration.script failed [View Less]

2 2

[asdf-devel] SBCL failure on test-configuration.script with latest ASDF
by Robert Goldman 08 Nov '11

08 Nov '11

I tested the latest ASDF from git with SBCL 1.0.47, and got the following test failure in test-configuration.script. Upgraded to SBCL head (SBCL 1.0.53.1-6b0e405) and I still get this test failure. Mac OS X, 64-bit, threading enabled (don't see why that would make a difference, but...). r

1 0

[asdf-devel] Best place to put a new config file?
by Zach Beane 05 Nov '11

05 Nov '11

If I'd like to extend the source registry by writing a registry configuration file somewhere, what's the best place to write that file? Is there a way to query the running system to get the answer? Is that necessary or is there some directory that is always good to use? Zach

3 6

[asdf-devel] maybe-add-tree.patch
by Сергей Катревич 03 Nov '11

03 Nov '11

Hi lispers! I am wrote micro patch for maybe-add-tree function. He to add :test #'equal in (find c (cdr it)) form. Finded small bug: (maybe-add-tree '((LOAD-OP (PREPARE-PREVALENCE-OP :WEBLOCKS-PREVALENCE)) (COMPILE-OP (COMPILE-OP "file1") (PREPARE-PREVALENCE-OP :WEBLOCKS-PREVALENCE))) 'COMPILE-OP 'COMPILE-OP "file1") => ((LOAD-OP (PREPARE-PREVALENCE-OP :WEBLOCKS-PREVALENCE)) (COMPILE-OP (COMPILE-OP "file1" "file1") (PREPARE-PREVALENCE-OP :WEBLOCKS-… [View More]

2 1

[asdf-devel] Bug in directory-files
by Pascal Costanza 01 Nov '11

01 Nov '11

Hi, There is a problem in the function directory-files (at least for LispWorks). Currently it is defined like this: (defun* directory-files (directory &optional (pattern *wild-file*)) (when (wild-pathname-p directory) (error "Invalid wild in ~S" directory)) (unless (member (pathname-directory pattern) '(() (:relative)) :test 'equal) (error "Invalid file pattern ~S" pattern)) (let ((entries (ignore-errors (directory* (merge-pathnames* pattern directory))))) (filter-… [View More]

3 3

[asdf-devel] OS X test results on latest ASDF
by Robert Goldman 23 Oct '11

23 Oct '11

Ran 35 tests: 35 passing and 0 failing all tests apparently successful Using alisp -q -batch Ran 35 tests: 35 passing and 0 failing all tests apparently successful Using mlisp -q -batch Ran 35 tests: 35 passing and 0 failing all tests apparently successful Using /Users/rpg/ccl/dx86cl64 --no-init --quiet --batch Ran 35 tests: 35 passing and 0 failing all tests apparently successful Using clisp -norc -ansi -I -on-error exit Ran 35 tests: 35 passing and 0 failing all tests … [View More]

3 6

[asdf-devel] run-shell-command
by Robert Goldman 21 Oct '11

21 Oct '11

Question: could we handle this problem with the new asdf contrib idea? Could we distribute an ASDF:RUN-SHELL-COMMAND based in the XCVB code base along with ASDF using a contrib system? I am reluctant to see RUN-SHELL-COMMAND no longer be distributed with ASDF, since it seems to make a hash of our claims that ASDF can manage systems that mix other code with common lisp code. I don't believe that invoking external facilities should rely on additional ASDF system dependencies. But I am … [View More]

2 3

[asdf-devel] Please test ASDF 2.017.22 as release candidate
by Faré 21 Oct '11

21 Oct '11

Dear ASDF users, can you please test ASDF 2.017.22? I'm declaring a feature freeze for ASDF until release, and assuming no bug is found and bugfix committed, the current ASDF will be promoted as 2.018 by the end of the month. The repository is still open for documentation and test updates. On the other hand, for any extensions you might want to publish, (for instance, around hooks for package renamings), I've created a asdf-contrib.git repo, currently empty save for a trival .asd file, next … [View More]to the asdf.git repo: ssh://common-lisp.net/project/asdf/git/asdf-contrib.git git://common-lisp.net/projects/asdf/asdf-contrib.git Changes since 2.017: * Solved a bug due to ASDF reusing components even when the ASDF definition has changed wildly, leading to bad behavior in incremental compilation and sometimes total failure of compilation of a new version. (Thanks to Xach for reporting and RPGoldman for fixing.) * Bind *default-pathname-defaults* around load-sysdef, to increase chances of successful pathname parsing in defsystem. * Many implementation specific improvements for ECL: merge with the ECL upstream version, support for the bytecode compiler, * Fix an issue with ASDF doing the wrong thing in case of a clock skew, thanks to Andreas Fuchs. * Simplification of the internals of perform-with-restarts and traverse's do-dep, that should fix some corner cases and make it easier to extend or further fix. There scarily doesn't remain any unedited code from Dan Barlow's original ASDF, though much of the interface design is preserved. * Improvements to tests and documentation. * Upgrade code slightly simplified, with a particular fix for CLISP; it is now tested on all supported implementations, not just SBCL. * Fixed run-shell-command on allegro/unix and clisp, documented the function, noted how it mightn't do what you think on Windows, marked it as obsolete, promoted as an official replacement my new xcvb-driver:run-program/process-output-stream * New :around-compile hook so you can control the syntax, optimization, and warning level, rename packages and balance compile-time side-effects, etc., around the compilation of files in your own modules. * Because it is required at least on ABCL, made the Unix vs Windows detection a runtime rather than compile-time distinction No more asdf-unix or asdf-windows feature, but (asdf::os-unix-p) and (asdf::os-windows-p) functions (not exported for now). Also recognize darwin as Unix ECL. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org No man would listen to you talk if he didn't know it was his turn next. — Edgar Watson Howe [View Less]

1 0

[asdf-devel] asdf and windows vs unix on abcl
by Faré 21 Oct '11

21 Oct '11

ABCL is special in that it can run on either Windows or Unix. The problem is that ASDF 2.017 determines which of Windows or Unix at compile-time, which causes confusion when ABCL's builtin ASDF is compiled on Windows and used on Unix or vice-versa. And I can tell your binary was definitely produced on Windows. (I found this issue while testing cl-launch. I also noticed that you fixed your ext:*command-line-argument-list* albeit in a necessarily incompatible way.) I suppose the solution is … [View More]

3 3

[asdf-devel] compile-with-nicknames
by Gábor Balázs 20 Oct '11

20 Oct '11

hY, I would like to propose a kind of an enhancement to the ASDF functionalities. So there is a problem with package nicknames that they have to be unique. So using the :nicknames option in a package definition can cause "uncorrectable" collisions. On the other hand, by not doing so, one has to use fully qualified package names (eg. :com.gigamonkeys.macro-utilities) during library development which makes the code completely unreadable (in my opinion at least). So there would be a possibility … [View More]

4 26