[asdf-devel] CCL build failure
CCL 1.8 on Mac OS X fails to compile asdf as pulled just now. Not-very-helpful transcript snippet: COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] Toplevel Forms... Toplevel Forms... Toplevel Forms... Toplevel Forms... ions of (:METHOD PERFORM (LOAD-OP CL-SOURCE-FILE)), in this file Testsuite failed: ASDF compiled with ERRORS Interactively, interestingly, when I try to build from an asdf:*central-registry* with home:lisp;asdf; in it, I get this error: Error while trying to load definition for system asdf from pathname home:lisp;asdf;asdf.asd.newest: Illegal logical namestring /Users/rpg/lisp/asdf/asdf.asd [Condition of type ASDF:LOAD-SYSTEM-DEFINITION-ERROR] No idea what that's about. When I use /Users/rpg/lisp/asdf/ instead, it works fine. Interactively, I get: ;Compiler warnings for home:lisp;asdf;asdf.lisp.newest : ; In an anonymous lambda form at position 220553: Duplicate definitions of (:METHOD PERFORM (LOAD-OP CL-SOURCE-FILE)), in this file ; Warning: COMPILE-FILE failed while performing #COMPILE-OP on #CL-SOURCE-FILE asdf asdf. ; While executing: #STANDARD-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE), in process repl-thread(14). ; Warning: COMPILE-FILE warned while performing #COMPILE-OP on #CL-SOURCE-FILE asdf asdf. ; While executing: #STANDARD-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE), in process repl-thread(14). So are the redefinitions breaking the update? ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] CCL build failure
On Tue, Jan 8, 2013 at 2:36 PM, Robert Goldman rpgold...@sift.info wrote: CCL 1.8 on Mac OS X fails to compile asdf as pulled just now. Not-very-helpful transcript snippet: COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] Toplevel Forms... Toplevel Forms... Toplevel Forms... Toplevel Forms... ions of (:METHOD PERFORM (LOAD-OP CL-SOURCE-FILE)), in this file Testsuite failed: ASDF compiled with ERRORS Interactively, interestingly, when I try to build from an asdf:*central-registry* with home:lisp;asdf; in it, I get this error: Error while trying to load definition for system asdf from pathname home:lisp;asdf;asdf.asd.newest: Illegal logical namestring /Users/rpg/lisp/asdf/asdf.asd [Condition of type ASDF:LOAD-SYSTEM-DEFINITION-ERROR] No idea what that's about. When I use /Users/rpg/lisp/asdf/ instead, it works fine. Whoa. Something funky is happening. Mind the logical. Something quite illogical is happening as the result of an attempted merge of pathnames with a logical pathname, presumably the home: thing. Can you explain me how logical pathnames are used on your machine and in your ASDF configuration? It's quite possible that I may have gotten some host defaulting mixed up somewhere. PS: I've exploded asdf into bits. See branch exploded on git. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org Politicians are like diapers: they must be changed often. And for the same reasons. [Also, adults don't need either of them. — Faré] ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] CCL build failure
On 1/8/13 Jan 8 -5:34 PM, Faré wrote: On Tue, Jan 8, 2013 at 2:36 PM, Robert Goldman rpgold...@sift.info wrote: CCL 1.8 on Mac OS X fails to compile asdf as pulled just now. Not-very-helpful transcript snippet: COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] COMPONENT-DEPENDS-ON [Defmethod] Toplevel Forms... Toplevel Forms... Toplevel Forms... Toplevel Forms... ions of (:METHOD PERFORM (LOAD-OP CL-SOURCE-FILE)), in this file Testsuite failed: ASDF compiled with ERRORS Interactively, interestingly, when I try to build from an asdf:*central-registry* with home:lisp;asdf; in it, I get this error: Error while trying to load definition for system asdf from pathname home:lisp;asdf;asdf.asd.newest: Illegal logical namestring /Users/rpg/lisp/asdf/asdf.asd [Condition of type ASDF:LOAD-SYSTEM-DEFINITION-ERROR] No idea what that's about. When I use /Users/rpg/lisp/asdf/ instead, it works fine. Whoa. Something funky is happening. Mind the logical. Something quite illogical is happening as the result of an attempted merge of pathnames with a logical pathname, presumably the home: thing. Can you explain me how logical pathnames are used on your machine and in your ASDF configuration? I was using this: (setf (logical-pathname-translations home) (list (list **;*.*.* /Users/rpg/**/*.*))) Gives me portability across Mac (/Users) and Linux (/home). and doing (push home:lisp;asdf; asdf:*central-registry*) (asdf:load-system asdf) viz: CL-USER (logical-pathname-translations home) ((#Phome:**;*.*.* #P/Users/rpg/**/*.*)) CL-USER (push home:lisp;asdf; asdf:*central-registry*) (home:lisp;asdf; #P/Users/rpg/lisp/xophe-clx/ ~/lisp/asdf-systems/ ~/lisp/asdf-install-systems/systems/ ~/lisp/asdf-systems/ ~/lisp/asdf-install-systems/systems/) CL-USER (asdf:load-system asdf) Unfortunately, on my copy of SLIME, attempts to inspect this illegal logical pathname object crashes the inspector. Something weird seems to be going on inside CCL: 0: ((:INTERNAL ASDF::LOAD-SYSDEF) #SIMPLE-ERROR #x302000D7344D) 1: (SIGNAL #SIMPLE-ERROR #x302000D7344D) 2: (CCL::%ERROR #SIMPLE-ERROR #x302000D7344D (/Users/rpg/lisp/asdf/asdf.asd) 7841373) Locals: CONDITION = #SIMPLE-ERROR #x302000D7344D CCL::ARGS = (/Users/rpg/lisp/asdf/asdf.asd) CCL::ERROR-POINTER = 7841373 3: (CCL::STRING-TO-PATHNAME /Users/rpg/lisp/asdf/asdf.asd 0 29 home #Phome:lisp;asdf;) 4: (CCL::FIND-LOAD-FILE #Phome:lisp;asdf;asdf.asd.newest) Locals: CCL::FILE-NAME = #Phome:lisp;asdf;asdf.asd.newest CCL::FULL-NAME = #P/Users/rpg/lisp/asdf/asdf.asd CCL::KIND = NIL CCL::FILE-TYPE = asd CCL::MERGED = #Phome:lisp;asdf;asdf.asd.newest 5: (CCL::%LOAD #Phome:lisp;asdf;asdf.asd.newest NIL NIL :ERROR :DEFAULT) 6: (LOAD #Phome:lisp;asdf;asdf.asd.newest :VERBOSE NIL :PRINT NIL :IF-DOES-NOT-EXIST :ERROR :EXTERNAL-FORMAT :DEFAULT) 7: ((:INTERNAL ASDF::LOAD-SYSDEF)) CL-USER (describe *fn*) #Phome:lisp;asdf;asdf.asd.newest Type: LOGICAL-PATHNAME Class: #BUILT-IN-CLASS LOGICAL-PATHNAME TYPE: (LOGICAL-PATHNAME . #CCL::CLASS-WRAPPER LOGICAL-PATHNAME #x300040039A2D) 1: (:ABSOLUTE lisp asdf) 2: asdf 3: asd %LOGICAL-PATHNAME-HOST: home %LOGICAL-PATHNAME-VERSION: :NEWEST ; No value CL-USER #P/Users/rpg/lisp/asdf/asdf.asd #P/Users/rpg/lisp/asdf/asdf.asd CL-USER (describe *) #P/Users/rpg/lisp/asdf/asdf.asd Type: PATHNAME Class: #BUILT-IN-CLASS PATHNAME TYPE: (PATHNAME . #CCL::CLASS-WRAPPER PATHNAME #x3000400399AD) %PATHNAME-DIRECTORY: (:ABSOLUTE Users rpg lisp asdf) %PATHNAME-NAME: asdf %PATHNAME-TYPE: asd %PHYSICAL-PATHNAME-VERSION: :NEWEST %PHYSICAL-PATHNAME-DEVICE: NIL It does look like FIND-SYSTEM is implicated, as witness the comparison between me checking the logical pathname object created by ASDF, and checking one I make myself: CL-USER (asdf:load-system asdf) #Phome:lisp;asdf;asdf.asd.newest #Phome:lisp;asdf;asdf.asd.newest CL-USER (setf *sys* *) #Phome:lisp;asdf;asdf.asd.newest CL-USER (probe-file *sys*) ; Evaluation aborted on #SIMPLE-ERROR #x302000DFD97D. ; Evaluation aborted on #SIMPLE-ERROR #x302000DFD97D. CL-USER CL-USER (probe-file home:lisp;asdf;asdf.asd) #P/Users/rpg/lisp/asdf/asdf.asd I must go off, sorry -- I'll see if I can dig up any more information. If you can suggest where to look, that would be great. cheers, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] deprecating run-shell-command
On Tue, Jan 8, 2013 at 11:09 PM, Daniel Herring dherr...@tentpost.com wrote: On Sun, 6 Jan 2013, Faré wrote: I will add a concatenate-all-source-op that recursively descends into all system dependencies, concatenates all sources, and creates the output file asdf.lisp, also including defsystem fallback stubs to make upgrade easier, just like the current asdf defsystem fallback stub. This way, ASDF can enjoy the advantages of both a large set of small libraries and a single-file bootstrap solution. Also, adding new extensions to ASDF will be easier. It's done in branch exploded, which also creates one package per file, in the style of faslpath and/or quick-build. I can't merge it to master until I write a variant of defpackage that will make the thing survive hot upgrade, but it's already a major cleanup. For the first time ever, ASDF sources are well-organized and mostly readable — and they are much more correct/robust, too. That sounds like it could be a very useful feature in general. For example, it would allow any program to be distributed with its all dependencies in a single source file. Yes, with limitations: 1- you mustn't rely on load-time effects of previous files during the compile-time of your file, unless they've been explicitly wrapped in an eval-when. 2- all your files must have the same encoding. 3- if you have an around-compile hook, it must apply to all files, and be already defined in some specially loaded prelude. Also, I don't currently register fake/fallback systems for transcluded dependencies. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org If you don't like yourself, you *can't* like other people. — Robert Heinlein, Time Enough For Love ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
