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

[asdf-devel] Loading asdf.lisp fails on Lispworks 6.0
by Yves Vandriessche 11 Mar '10

11 Mar '10

Loading the latest asdf.lisp ;;; hash - 7e34af2cdcb62c007ac4751bbbff543dd7d117ba In Lispworks 6.0 yields the following error: > > CL-USER 1 > (load "~/Desktop/asdf") > ; Loading text file /Users/yvdriess/Desktop/asdf.lisp > > Error: Symbol "ENVIRONMENT-XIABLE" not found at all in the LISPWORKS > package. > 1 (continue) Make a new symbol. > 2 Try loading ~/Desktop/asdf again. > 3 Give up loading ~/Desktop/asdf. > 4 Try loading another file instead of ~/Desktop/asdf. > 5 (abort) Return to level 0. > 6 Return to top loop level 0. > > Type :b for backtrace or :c <option number> to proceed. > Type :bug-form "<subject>" for a bug report template or :? for other > options. > > ASDF 2 : 1 > :b > Call to ERROR > Call to CERROR > Call to (HARLEQUIN-COMMON-LISP:SUBFUNCTION 1 LOAD) > Call to LOAD > Call to EVAL > Call to CAPI::CAPI-TOP-LEVEL-FUNCTION > Call to CAPI::INTERACTIVE-PANE-TOP-LOOP > Call to MP::PROCESS-SG-FUNCTION An older version of asdf.lisp still works though, $Revision: 1.118 $

2 1

[asdf-devel] A dream for ASDF2
by nuntius＠strider2.example.org 11 Mar '10

11 Mar '10

Tobias C. Rittweiler wrote: Re: [asdf-devel] Is this necessary in this form? Re: ASDF 1.501 > Isn't asdf-output-locations somewhat like a CL pendant to `make install' > if you squint your eyes? > > Shouldn't that be an integral part of ASDF? Exactly yes and absolutely no. Not necessarily in that order. My issue is that there is a great similarity; this similarity is driven by a need inherent in the use of libraries; but ASDF (due to history) has certain things absolutely backwards. There are many users that a build system must support. - developers do incremental compiles - maintainer creates a release (builds sources, docs, etc. into a self-contained archive) - maintainer checks that the release actually builds, cleans, installs, etc. - user or system integrator configures the release for local needs - the release is compiled (often into a separate directory or on a separate computer) - the release is tested (before install) - the release is installed (often to a read-only space, as root, or into a temporary directory that will be archived for distribution) - the release is loaded (often without sources) - the release is uninstalled ASDF needs a coherent story for the person doing each of these jobs. Instead, the current model lumps most everything into a single "load-op", and there is no principled way to perform or configure each of the above phases separately. My biggest concern with the recent changes is that they build a big scaffold that institutionalizes a design in need of fundamental changes. Some parts of .asd files may need incompatible changes; but I think most uses are completely upgradeable. However, I do not think the recent ASDF proposals will be. I would like the ASDF architecture to look something like - bootstrap a few (self-contained) core utils using a special install sequence (simple COMPILE, test, and install scripts) - ASDF uses LOAD to pull these in; as each loads, more functionality becomes available (aka SBCL boostrap). - All other packages can now be built with the full ASDF. - (optional) ASDF may upgrade itself without the bootstrap sequence. ASDF features I would like: - Standard way to pass configuration options to ASDF for building a specific system. For example, ASDF should let me configure which compression backend cl-pdf uses, and ASDF should write these choices to file for me. This should be a replayable config file that can be modified for reconfiguration, or read in for compilation and install. I should be able to have several builds at once, each with a different set of choices. - Standard options for each system. For example, a popular one might allow ASDF to autorecompile fasls when the sources change. Another would be an install prefix. Another is to modify the installed system name (e.g. add version info; asdf-1.5 would load the ASDF package, version 1.5). Another to enable the system config cache (below). - Generic configuration cache, independent of use. In other words, a simple configuration format where I can set key/value pairs. Some of which may happen to control ASDF source locations, others may control ASDF output locations, yet others may be defined by end-user ASDF files. This cache should have three levels, one for the sysadmin, one for the user, and one for inside the system configuration area (usually the source tree). Compare the autoconf site configuration mechanism. http://www.gnu.org/software/autoconf/manual/html_node/Site-Configuration.ht… - ASDF compile/install spits out a system.fasl. Semantically, loading this causes the entire library to be loaded. On some CL's, it might simply be the concatenation of the compiled source files; on others, it might LOAD them all in order. The above is a long-enough list for today. I think it covers most of the bases. These things aren't problems I'm creating; they are lessons I have gleaned from GNU autotools and other build systems. Whenever ASDF takes a shortcut, we have issues. For example, "" # We still need to find a way to precompile libraries # Because asdf is now taking care of placing the fasl file in the correct place, we cannot remove fasls for a specific implementation or library, so we nuke them all. Not optimal. "" - http://pvaneynd.livejournal.com/133491.html These are part of the standard autotools procedure; they represent a couple use cases from the first list above. Later, Daniel P.S. Here's a draft response I penned for an earlier post Subject: Re: [asdf-devel] ASDF 1.501 > Next, comes a similar revamp of ASDF-BINARY-LOCATIONS configuration. > Or maybe a wholesale replacement of ABL with something that's simpler > and configured in a way similar to source-registry? What do YOU think? What do I really think? Its great that ASDF is getting some TLC, but the whole "register the sources" thing is fundamentally flawed. >From the end-user's perspective, the whole purpose of a "defsystem" (henceforth library loader) is to get one or more packages into the running lisp.

2 1

[asdf-devel] Error when loading asdf.lisp: Package "LINUX" does not exist
by alberich 11 Mar '10

11 Mar '10

Hello, I'm using opensuse 4.3 and clisp 2.44.1 When trying to load asdf.lisp (git-version), load breaks with the error message that package "LINUX" did not exist (line 500). I could, however not find a file defining a "linux" package. After commenting out ; #+clisp (defun get-uid () (linux:getuid)) loading asdf.lisp works fine. Still, when trying to load asdf-install.lisp, load stops with the error message that the file SB-POSIX did not exist. Any ideas? Regards Alain Berich

2 1

[asdf-devel] Q about ASDF on LW
by Daniel Herring 11 Mar '10

11 Mar '10

Hi all, ---------- Forwarded message ---------- Date: Wed, 20 Jan 2010 10:09:39 GMT From: Nick Levine <ndl(a)ravenbrook.com> Reply-To: Discuss changes to LibCL <libcl-devel(a)lists.libcl.com> Subject: Re: [LibCL-devel] [ann] libcl-2010-01-18-snapshot > All the above was with LW 6.0. I also tried LW 5.1.2 and got a > stack overflow loading alexandria\alexandria.asd Odd; this snapshot contains the same alexandria as the last beta... I suspect it's an ASDF thing rather than anything to do with Alexandria. Where shall I send the backtrace? Btw this is fixed by compiling asdf rather than loading it into LW as interpretted source. --------------------------------------- Can an ASDF developer reproduce this on LW5? Is there a good reason to need a compiled ASDF, or would LW benefit from an extra eval-when or finalize-instance somewhere? If we should always compile, is there a way to use asdf-binary-locations to control the dump of the ASDF fasl? Thanks, Daniel P.S. alexandria.asd last changed on 2008-11-23.

4 9

[asdf-devel] asdf.texinfo version 1.375 has errors [resend as ML member]
by Peter Van Eynde 11 Mar '10

11 Mar '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, While trying to build a new Debian package I get the following errors: > $ makeinfo --verbose asdf.texinfo > makeinfo (GNU texinfo) 4.13 > Making info file `asdf.info' from `asdf.texinfo'. > Formatting node Top... > Formatting node Introduction... > Formatting node Using asdf to load systems... > Formatting node Defining systems with defsystem... > Formatting node The defsystem form... > Formatting node A more involved example... > Formatting node The defsystem grammar... > Formatting node Other code in .asd files... > Formatting node The object model of asdf... > Formatting node Operations... > Formatting node Predefined operations of asdf... > Formatting node Creating new operations... > Formatting node Components... > Formatting node Common attributes of components... > Formatting node Pre-defined subclasses of component... > Formatting node Creating new component types... > Formatting node Controlling where ASDF saves compiled files... > Formatting node Error handling... > Formatting node Compilation error and warning handling... > Formatting node Miscellaneous additional functionality... > Formatting node Getting the latest version... > Formatting node FAQ... > Formatting node TODO list... > Formatting node missing bits in implementation... > Formatting node Inspiration... > Formatting node Concept Index... > Formatting node Function and Class Index... > Formatting node Variable Index... > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1301: Prev field of node `FAQ' not pointed to. > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1451: This node (missing bits in implementation) has the bad Next. > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1281: Node `Getting the latest version' lacks menu item for `FAQ' despite being its Up target. > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1281: Next field of node `Getting the latest version' not pointed to (perhaps incorrect sectioning?). > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1301: This node (FAQ) has the bad Prev. This is fixed with the trivial patch: > diff --git a/asdf.texinfo b/asdf.texinfo > index 3d379e4..ddefe01 100644 > --- a/asdf.texinfo > +++ b/asdf.texinfo > @@ -1298,7 +1298,7 @@ You will find the above referenced tags in this repository. > Discussion of ASDF development is conducted on the mailing list > @kbd{asdf-devel@@common-lisp.net}. > > -@node FAQ, TODO list, missing bits in implementation, Getting the latest version, Top > +@node FAQ, TODO list, Getting the latest version, Top > @comment node-name, next, previous, up > @chapter FAQ See also http://git.debian.org/?p=pkg-common-lisp/cl-asdf.git;a=commit;h=ea3aa53b623… Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson| -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJLVVNrAAoJEB4VNT76eIlawy4QAKUEa/QOLfuKZCvCthVmPj0p 6PuLzfmpGM7jJ+7fsx0WQEAHgE/9RkFL9emC8diAPRiAXCBdB1ypZ9uciniYtc1Y x7/5QL2vpJH9NYmMlK6xKE2l0doYAe2sgSSt6BzvFpvXdnv7mt1Il5CmN93RtJQI 9RUm7aei+uqN1n+tojNw37OMa0YC2x/hSdjPdqTyDqm3gDa0kUYXDfTHomlcBBRP tavFqwLvqfZ3LlbIiObJqCu6eh35gpCW6O1AmdG/dXAGfzjoKV7tlR8nvfIoCBsu P6XUi32P0K0H2fGfJ55ETjszJSwb735aWvAlaNHuZV6Z7xa5uLKJ9FTraY+4K2i6 j7swacO/NJla3m8eOVaZF+6wZEuiWZpODSH0u6eo0JSlCX6OpGO41q4uQ6iJA7Pz nj5e0kEejnamk9IfLVAFPL8kpz7HfxreEVGr83iP4/At6JKOAO3YbOfwcL0/po51 2b+eqkZNsZqmolrJK0hQqIN5A0LhuyQ4CVr/o9xulx08MZkHCnNYC7t2cLBMWBjG hYx5exF2iqlnOlF7IZ74qdjRye9ykZ8aOs24zvSX6gWwzfyniLZoEYuH8sNrEWD1 queXBogs4Wqmda50gICYw6ADmplcCpQfnI2/f+DfjH6JSnxv4dbYcCD7hqwrlkS3 KDuVd4nSxQ3BhfQ2NSi3 =0l7y -----END PGP SIGNATURE-----

2 2

Re: [asdf-devel] ASDF testing
by Faré 28 Feb '10

28 Feb '10

Apparently, in script-support.lisp, the leave-lisp implementation for lispworks is broken. Can you fix it? Renaming "code" to "return" might or might not be enough. Next time you have an error, can you include a backtrace? Thanks a *lot* for your debugging help. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The socialist says: "From each according to his ability, to each according to his need." What it really advocates in practice: "From each according to his gullibility, to each according to his greed." On 27 February 2010 21:25, David McClain <dbm(a)refined-audiometrics.com> wrote: > Yes, (1) I am using what I downloaded yesterday after your most recent > changes. File asdf-44ae9b1f75dac2d4e62bf1c25ba85cb373737ceb.tar > And your hint about a softlink was wonderful... Instead, I just changed the > script to state LWM64 wherever LISPWORKS was mentioned... Here are the > results... > > bash-3.2$ run-tests.sh lwm64 > lwm64 is /users/dbmcclain/projects/bin/lwm64 > /users/dbmcclain/projects/bin/lwm64 -siteinit - -init - > LispWorks(R): The Common Lisp Programming Environment > Copyright (C) 1987-2009 LispWorks Ltd. All rights reserved. > Version 6.0.0 > Saved by dbmcclain as lwm64, at 27 Feb 2010 6:37 > User dbmcclain on RoadKill.local > ; Loading text file /Users/dbmcclain/Downloads/asdf/test/compile-asdf.lisp > ; Loading text file > /Users/dbmcclain/Downloads/asdf/test/script-support.lisp > ;;; Compiling file /Users/dbmcclain/Downloads/asdf/asdf.lisp ... > ;;; Safety = 3, Speed = 1, Space = 1, Float = 1, Interruptible = 1 > ;;; Compilation speed = 1, Debug = 2, Fixnum safety = 3 > ;;; Source level debugging is on > ;;; Source file recording is on > ;;; Cross referencing is on > ; (TOP-LEVEL-FORM 0) > ; (TOP-LEVEL-FORM 1) > ; (TOP-LEVEL-FORM 3) > ; (TOP-LEVEL-FORM 4) > ; (DEFPARAMETER ASDF::*ASDF-VERSION*) > ; ASDF:ASDF-VERSION > ; (DEFVAR ASDF:*RESOLVE-SYMLINKS*) > ; (DEFVAR ASDF:*COMPILE-FILE-WARNINGS-BEHAVIOUR*) > ; (DEFVAR ASDF:*COMPILE-FILE-FAILURE-BEHAVIOUR*) > ; (DEFVAR ASDF::*VERBOSE-OUT*) > ; (DEFPARAMETER ASDF::+ASDF-METHODS+) > ; (TOP-LEVEL-FORM 12) > ; (TOP-LEVEL-FORM 12) > ; (METHOD-COMBINATION ASDF:STANDARD-ASDF-METHOD-COMBINATION) > ; (TOP-LEVEL-FORM 14) > ; (DEFGENERIC ASDF:PERFORM) > ; (DEFGENERIC ASDF:OPERATION-DONE-P) > ; (DEFGENERIC ASDF:EXPLAIN) > ; (DEFGENERIC ASDF:OUTPUT-FILES) > ; (DEFGENERIC ASDF:INPUT-FILES) > ; (DEFGENERIC ASDF:SYSTEM-SOURCE-FILE) > ; (DEFGENERIC ASDF:COMPONENT-SYSTEM) > ; (DEFGENERIC ASDF:COMPONENT-PATHNAME) > ; (DEFGENERIC ASDF:COMPONENT-RELATIVE-PATHNAME) > ; (DEFGENERIC ASDF:COMPONENT-PROPERTY) > ; (DEFGENERIC (SETF ASDF:COMPONENT-PROPERTY)) > ; (DEFGENERIC ASDF::VERSION-SATISFIES) > ; (DEFGENERIC ASDF:FIND-COMPONENT) > ; (DEFGENERIC ASDF:SOURCE-FILE-TYPE) > ; (DEFGENERIC ASDF::OPERATION-ANCESTOR) > ; (DEFGENERIC ASDF::COMPONENT-VISITED-P) > ; (DEFGENERIC ASDF::VISIT-COMPONENT) > ; (DEFGENERIC (SETF ASDF::VISITING-COMPONENT)) > ; (DEFGENERIC ASDF::COMPONENT-VISITING-P) > ; (DEFGENERIC ASDF:COMPONENT-DEPENDS-ON) > ; (DEFGENERIC ASDF::COMPONENT-SELF-DEPENDENCIES) > ; (DEFGENERIC ASDF::TRAVERSE) > ; (DEFGENERIC ASDF::OUTPUT-FILES-USING-MAPPINGS) > ; ASDF-UTILITIES:AIF > ; ASDF-UTILITIES:PATHNAME-SANS-NAME+TYPE > ; ASDF-UTILITIES:PATHNAME-DIRECTORY-PATHNAME > ; ASDF-UTILITIES:APPENDF > ; ASDF-UTILITIES:ASDF-MESSAGE > ; ASDF-UTILITIES:SPLIT > ; ASDF-UTILITIES:COMPONENT-NAME-TO-PATHNAME-COMPONENTS > ; ASDF-UTILITIES:REMOVE-KEYS > ; ASDF-UTILITIES:REMOVE-KEYWORD > ; ASDF-UTILITIES:RESOLVE-SYMLINKS > ; ASDF-UTILITIES:GETENV > ; ASDF-UTILITIES:DIRECTORY-PATHNAME-P > ; ASDF-UTILITIES:ENSURE-DIRECTORY-PATHNAME > ; ASDF-UTILITIES:ABSOLUTE-PATHNAME-P > ; ASDF-UTILITIES:LENGTH=N-P > ; ASDF-UTILITIES:ENDS-WITH > ; ASDF-UTILITIES:MAKE-COLLECTOR > ; ASDF-UTILITIES:READ-FILE-FORMS > ; ASDF-UTILITIES:GET-UID > ; ASDF-UTILITIES:TRUENAMIZE > ; (SUBFUNCTION (DEFCLASS ASDF:SYSTEM-DEFINITION-ERROR) (DEFINE-CONDITION > ASDF:SYSTEM-DEFINITION-ERROR)) > ; (DEFINE-CONDITION ASDF:SYSTEM-DEFINITION-ERROR) > ; (SUBFUNCTION (DEFCLASS ASDF::FORMATTED-SYSTEM-DEFINITION-ERROR) > (DEFINE-CONDITION ASDF::FORMATTED-SYSTEM-DEFINITION-ERROR)) > ; (DEFINE-CONDITION ASDF::FORMATTED-SYSTEM-DEFINITION-ERROR) > ; (DEFINE-CONDITION ASDF::FORMATTED-SYSTEM-DEFINITION-ERROR) > ; (SUBFUNCTION (DEFCLASS ASDF:MISSING-DEFINITION) (DEFINE-CONDITION > ASDF:MISSING-DEFINITION)) > ; (DEFINE-CONDITION ASDF:MISSING-DEFINITION) > ; (DEFINE-CONDITION ASDF:MISSING-DEFINITION) > ; (SUBFUNCTION (DEFCLASS ASDF:CIRCULAR-DEPENDENCY) (DEFINE-CONDITION > ASDF:CIRCULAR-DEPENDENCY)) > ; (DEFINE-CONDITION ASDF:CIRCULAR-DEPENDENCY) > ; (SUBFUNCTION (DEFCLASS ASDF:DUPLICATE-NAMES) (DEFINE-CONDITION > ASDF:DUPLICATE-NAMES)) > ; (DEFINE-CONDITION ASDF:DUPLICATE-NAMES) > ; (SUBFUNCTION (DEFCLASS ASDF:MISSING-COMPONENT) (DEFINE-CONDITION > ASDF:MISSING-COMPONENT)) > ; (DEFINE-CONDITION ASDF:MISSING-COMPONENT) > ; (SUBFUNCTION (DEFCLASS ASDF:MISSING-COMPONENT-OF-VERSION) > (DEFINE-CONDITION ASDF:MISSING-COMPONENT-OF-VERSION)) > ; (DEFINE-CONDITION ASDF:MISSING-COMPONENT-OF-VERSION) > ; (SUBFUNCTION (DEFCLASS ASDF:MISSING-DEPENDENCY) (DEFINE-CONDITION > ASDF:MISSING-DEPENDENCY)) > ; (DEFINE-CONDITION ASDF:MISSING-DEPENDENCY) > ; (SUBFUNCTION (DEFCLASS ASDF:MISSING-DEPENDENCY-OF-VERSION) > (DEFINE-CONDITION ASDF:MISSING-DEPENDENCY-OF-VERSION)) > ; (DEFINE-CONDITION ASDF:MISSING-DEPENDENCY-OF-VERSION) > ; (SUBFUNCTION (DEFCLASS ASDF:OPERATION-ERROR) (DEFINE-CONDITION > ASDF:OPERATION-ERROR)) > ; (DEFINE-CONDITION ASDF:OPERATION-ERROR) > ; (DEFINE-CONDITION ASDF:OPERATION-ERROR) > ; (SUBFUNCTION (DEFCLASS ASDF:COMPILE-ERROR) (DEFINE-CONDITION > ASDF:COMPILE-ERROR)) > ; (DEFINE-CONDITION ASDF:COMPILE-ERROR) > ; (SUBFUNCTION (DEFCLASS ASDF:COMPILE-FAILED) (DEFINE-CONDITION > ASDF:COMPILE-FAILED)) > ; (DEFINE-CONDITION ASDF:COMPILE-FAILED) > ; (SUBFUNCTION (DEFCLASS ASDF:COMPILE-WARNED) (DEFINE-CONDITION > ASDF:COMPILE-WARNED)) > ; (DEFINE-CONDITION ASDF:COMPILE-WARNED) > ; (DEFCLASS ASDF:COMPONENT) > ; (METHOD PRINT-OBJECT (ASDF:MISSING-DEPENDENCY T)) > ; ASDF::SYSDEF-ERROR > ; (METHOD PRINT-OBJECT (ASDF:MISSING-COMPONENT T)) > ; (METHOD PRINT-OBJECT (ASDF:MISSING-COMPONENT-OF-VERSION T)) > ; (METHOD ASDF:COMPONENT-SYSTEM (ASDF:COMPONENT)) > ; (METHOD PRINT-OBJECT (ASDF:COMPONENT T)) > ; (DEFCLASS ASDF:MODULE) > ; ASDF::COMPONENT-PARENT-PATHNAME > ; (METHOD ASDF:COMPONENT-RELATIVE-PATHNAME (ASDF:MODULE)) > ; (METHOD ASDF:COMPONENT-PATHNAME (ASDF:COMPONENT)) > ; (METHOD ASDF:COMPONENT-PROPERTY (ASDF:COMPONENT T)) > ; (METHOD (SETF ASDF:COMPONENT-PROPERTY) (T ASDF:COMPONENT T)) > ; (DEFCLASS ASDF:SYSTEM) > ; (METHOD ASDF::VERSION-SATISFIES (ASDF:COMPONENT T)) > ; (METHOD ASDF::VERSION-SATISFIES (STRING T)) > ; ASDF::MAKE-DEFINED-SYSTEMS-TABLE > ; (DEFVAR ASDF::*DEFINED-SYSTEMS*) > ; ASDF-UTILITIES:COERCE-NAME > ; ASDF-UTILITIES:SYSTEM-REGISTERED-P > ; ASDF:MAP-SYSTEMS > ; (DEFPARAMETER ASDF:*SYSTEM-DEFINITION-SEARCH-FUNCTIONS*) > ; ASDF:SYSTEM-DEFINITION-PATHNAME > ; (DEFVAR ASDF:*CENTRAL-REGISTRY*) > ; ASDF::SYSDEF-CENTRAL-REGISTRY-SEARCH > ; ASDF::MAKE-TEMPORARY-PACKAGE > ; ASDF::SAFE-FILE-WRITE-DATE > ; ASDF:FIND-SYSTEM > ; ASDF::REGISTER-SYSTEM > ; (METHOD ASDF:FIND-COMPONENT (ASDF:MODULE T)) > ; (METHOD ASDF:FIND-COMPONENT ((EQL NIL) T)) > ; (DEFCLASS ASDF:SOURCE-FILE) > ; (DEFCLASS ASDF:CL-SOURCE-FILE) > ; (DEFCLASS ASDF:C-SOURCE-FILE) > ; (DEFCLASS ASDF:JAVA-SOURCE-FILE) > ; (DEFCLASS ASDF:STATIC-FILE) > ; (DEFCLASS ASDF:DOC-FILE) > ; (DEFCLASS ASDF:HTML-FILE) > ; (METHOD ASDF:SOURCE-FILE-TYPE (ASDF:CL-SOURCE-FILE ASDF:MODULE)) > ; (METHOD ASDF:SOURCE-FILE-TYPE (ASDF:C-SOURCE-FILE ASDF:MODULE)) > ; (METHOD ASDF:SOURCE-FILE-TYPE (ASDF:JAVA-SOURCE-FILE ASDF:MODULE)) > ; (METHOD ASDF:SOURCE-FILE-TYPE (ASDF:HTML-FILE ASDF:MODULE)) > ; (METHOD ASDF:SOURCE-FILE-TYPE (ASDF:STATIC-FILE ASDF:MODULE)) > ; ASDF::MERGE-COMPONENT-RELATIVE-PATHNAME > ; (METHOD ASDF:COMPONENT-RELATIVE-PATHNAME (ASDF:SOURCE-FILE)) > ; (DEFCLASS ASDF:OPERATION) > ; (METHOD PRINT-OBJECT (ASDF:OPERATION T)) > ; (METHOD SHARED-INITIALIZE :AFTER (ASDF:OPERATION T)) > ; ASDF::NODE-FOR > ; (METHOD ASDF::OPERATION-ANCESTOR (ASDF:OPERATION)) > ; ASDF::MAKE-SUB-OPERATION > ; (METHOD ASDF::VISIT-COMPONENT (ASDF:OPERATION ASDF:COMPONENT T)) > ; (METHOD ASDF::COMPONENT-VISITED-P (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD (SETF ASDF::VISITING-COMPONENT) (T T T)) > ; (METHOD (SETF ASDF::VISITING-COMPONENT) (T ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF::COMPONENT-VISITING-P (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF:COMPONENT-DEPENDS-ON (SYMBOL ASDF:COMPONENT)) > ; (METHOD ASDF:COMPONENT-DEPENDS-ON (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF::COMPONENT-SELF-DEPENDENCIES (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF:INPUT-FILES (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF:INPUT-FILES (ASDF:OPERATION ASDF:MODULE)) > ; (METHOD ASDF:OPERATION-DONE-P (ASDF:OPERATION ASDF:COMPONENT)) > ; (DEFVAR ASDF::*FORCING*) > ; (METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF:PERFORM (ASDF:OPERATION ASDF:SOURCE-FILE)) > ; (METHOD ASDF:PERFORM (ASDF:OPERATION ASDF:MODULE)) > ; (METHOD ASDF:EXPLAIN (ASDF:OPERATION ASDF:COMPONENT)) > ; (DEFCLASS ASDF:COMPILE-OP) > ; (METHOD ASDF:PERFORM :BEFORE (ASDF:COMPILE-OP ASDF:SOURCE-FILE)) > ; (METHOD ASDF:PERFORM :AFTER (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) > ; (METHOD ASDF:OUTPUT-FILES (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) > ; (METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:STATIC-FILE)) > ; (METHOD ASDF:OUTPUT-FILES (ASDF:COMPILE-OP ASDF:STATIC-FILE)) > ; (METHOD ASDF:INPUT-FILES (ASDF:COMPILE-OP ASDF:STATIC-FILE)) > ; (DEFCLASS ASDF::BASIC-LOAD-OP) > ; (DEFCLASS ASDF:LOAD-OP) > ; (METHOD ASDF:PERFORM (ASDF:LOAD-OP ASDF:CL-SOURCE-FILE)) > ; (METHOD ASDF:PERFORM ASDF:AROUND (ASDF:LOAD-OP ASDF:CL-SOURCE-FILE)) > ; (METHOD ASDF:PERFORM ASDF:AROUND (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) > ; (METHOD ASDF:PERFORM (ASDF:LOAD-OP ASDF:STATIC-FILE)) > ; (METHOD ASDF:OPERATION-DONE-P (ASDF:LOAD-OP ASDF:STATIC-FILE)) > ; (METHOD ASDF:OUTPUT-FILES (ASDF:OPERATION ASDF:COMPONENT)) > ; (METHOD ASDF:COMPONENT-DEPENDS-ON (ASDF:LOAD-OP ASDF:COMPONENT)) > ; (DEFCLASS ASDF:LOAD-SOURCE-OP) > ; (METHOD ASDF:PERFORM (ASDF:LOAD-SOURCE-OP ASDF:CL-SOURCE-FILE)) > ; (METHOD ASDF:PERFORM (ASDF:LOAD-SOURCE-OP ASDF:STATIC-FILE)) > ; (METHOD ASDF:OUTPUT-FILES (ASDF:LOAD-SOURCE-OP ASDF:COMPONENT)) > ; (METHOD ASDF:COMPONENT-DEPENDS-ON (ASDF:LOAD-SOURCE-OP ASDF:COMPONENT)) > ; (METHOD ASDF:OPERATION-DONE-P (ASDF:LOAD-SOURCE-OP ASDF:SOURCE-FILE)) > ; (DEFCLASS ASDF:TEST-OP) > ; (METHOD ASDF:PERFORM (ASDF:TEST-OP ASDF:COMPONENT)) > ; (METHOD ASDF:OPERATION-DONE-P (ASDF:TEST-OP ASDF:SYSTEM)) > ; (METHOD ASDF:COMPONENT-DEPENDS-ON :AROUND (ASDF:TEST-OP ASDF:SYSTEM)) > ; ASDF:OPERATE > ; ASDF:OOS > ; (TOP-LEVEL-FORM 167) > ; ASDF:LOAD-SYSTEM > ; ASDF:COMPILE-SYSTEM > ; ASDF:TEST-SYSTEM > ; ASDF::DETERMINE-SYSTEM-PATHNAME > ; ASDF:DEFSYSTEM > ; ASDF::CLASS-FOR-TYPE > ; ASDF::MAYBE-ADD-TREE > ; ASDF::UNION-OF-DEPENDENCIES > ; (DEFVAR ASDF::*SERIAL-DEPENDS-ON*) > ; ASDF::SYSDEF-ERROR-COMPONENT > ; ASDF::CHECK-COMPONENT-INPUT > ; ASDF::%REMOVE-COMPONENT-INLINE-METHODS > ; ASDF::%DEFINE-COMPONENT-INLINE-METHODS > ; ASDF::%REFRESH-COMPONENT-INLINE-METHODS > ; ASDF::PARSE-COMPONENT-FORM > ; ASDF:RUN-SHELL-COMMAND > ; (METHOD ASDF:SYSTEM-SOURCE-FILE (T)) > ; ASDF::SYSTEM-SOURCE-DIRECTORY > ; ASDF::RELATIVIZE-DIRECTORY > ; ASDF::RELATIVIZE-PATHNAME-DIRECTORY > ; ASDF:SYSTEM-RELATIVE-PATHNAME > ; (DEFPARAMETER ASDF::*IMPLEMENTATION-FEATURES*) > ; (DEFPARAMETER ASDF::*OS-FEATURES*) > ; (DEFPARAMETER ASDF::*ARCHITECTURE-FEATURES*) > ; ASDF::LISP-VERSION-STRING > ; ASDF::FIRST-FEATURE > ; ASDF::IMPLEMENTATION-TYPE > ; ASDF::IMPLEMENTATION-IDENTIFIER > ; ASDF::USER-CONFIGURATION-DIRECTORY > ; ASDF::SYSTEM-CONFIGURATION-DIRECTORY > ; ASDF::CONFIGURATION-INHERITANCE-DIRECTIVE-P > ; ASDF::VALIDATE-CONFIGURATION-FORM > ; ASDF::VALIDATE-CONFIGURATION-FILE > ; ASDF::VALIDATE-CONFIGURATION-DIRECTORY > ; (DEFVAR ASDF::*OUTPUT-TRANSLATIONS*) > ; (DEFVAR ASDF::*USER-CACHE*) > ; (DEFVAR ASDF::*SYSTEM-CACHE*) > ; ASDF::OUTPUT-TRANSLATIONS > ; (SETF ASDF::OUTPUT-TRANSLATIONS) > ; ASDF::OUTPUT-TRANSLATIONS-INITIALIZED-P > ; ASDF:CLEAR-OUTPUT-TRANSLATIONS > ; (DEFPARAMETER ASDF::*WILD-PATH*) > ; ASDF::WILDEN > ; ASDF::RESOLVE-ABSOLUTE-LOCATION-COMPONENT > ; ASDF::RESOLVE-RELATIVE-LOCATION-COMPONENT > ; ASDF::RESOLVE-LOCATION > ; ASDF::LOCATION-DESIGNATOR-P > ; ASDF::VALIDATE-OUTPUT-TRANSLATIONS-DIRECTIVE > ; ASDF::VALIDATE-OUTPUT-TRANSLATIONS-FORM > ; ASDF::VALIDATE-OUTPUT-TRANSLATIONS-FILE > ; ASDF::VALIDATE-OUTPUT-TRANSLATIONS-DIRECTORY > ; ASDF::PARSE-OUTPUT-TRANSLATIONS-STRING > ; (DEFPARAMETER ASDF::*DEFAULT-OUTPUT-TRANSLATIONS*) > ; (DEFPARAMETER ASDF::*IMPLEMENTATION-OUTPUT-TRANSLATIONS*) > ; ASDF::IMPLEMENTATION-OUTPUT-TRANSLATIONS > ; (DEFPARAMETER ASDF::*OUTPUT-TRANSLATIONS-FILE*) > ; (DEFPARAMETER ASDF::*OUTPUT-TRANSLATIONS-DIRECTORY*) > ; ASDF::USER-OUTPUT-TRANSLATIONS-PATHNAME > ; ASDF::SYSTEM-OUTPUT-TRANSLATIONS-PATHNAME > ; ASDF::USER-OUTPUT-TRANSLATIONS-DIRECTORY-PATHNAME > ; ASDF::SYSTEM-OUTPUT-TRANSLATIONS-DIRECTORY-PATHNAME > ; ASDF::ENVIRONMENT-OUTPUT-TRANSLATIONS > ; (DEFGENERIC ASDF::PROCESS-OUTPUT-TRANSLATIONS) > ; (METHOD ASDF::PROCESS-OUTPUT-TRANSLATIONS (SYMBOL)) > ; (METHOD ASDF::PROCESS-OUTPUT-TRANSLATIONS (PATHNAME)) > ; (METHOD ASDF::PROCESS-OUTPUT-TRANSLATIONS (STRING)) > ; (METHOD ASDF::PROCESS-OUTPUT-TRANSLATIONS (NULL)) > ; (METHOD ASDF::PROCESS-OUTPUT-TRANSLATIONS (CONS)) > ; ASDF::INHERIT-OUTPUT-TRANSLATIONS > ; ASDF::PROCESS-OUTPUT-TRANSLATIONS-DIRECTIVE > ; ASDF:INITIALIZE-OUTPUT-TRANSLATIONS > ; ASDF:ENSURE-OUTPUT-TRANSLATIONS > ; ASDF:APPLY-OUTPUT-TRANSLATIONS > ; (METHOD ASDF:OUTPUT-FILES :AROUND (ASDF:OPERATION ASDF:COMPONENT)) > ; ASDF:COMPILE-FILE-PATHNAME* > ; (DEFPARAMETER ASDF::*LINK-INITIAL-DWORD*) > ; (DEFPARAMETER ASDF::*LINK-GUID*) > ; ASDF::READ-NULL-TERMINATED-STRING > ; ASDF::READ-LITTLE-ENDIAN > ; ASDF::PARSE-FILE-LOCATION-INFO > ; ASDF::PARSE-WINDOWS-SHORTCUT > ; (TOP-LEVEL-FORM 249) > ; (DEFVAR ASDF::*DEFAULT-EXCLUSIONS*) > ; (DEFVAR ASDF::*SOURCE-REGISTRY*) > ; ASDF::SOURCE-REGISTRY > ; (SETF ASDF::SOURCE-REGISTRY) > ; ASDF::SOURCE-REGISTRY-INITIALIZED-P > ; ASDF:CLEAR-SOURCE-REGISTRY > ; ASDF::SYSDEF-SOURCE-REGISTRY-SEARCH > ; ASDF::VALIDATE-SOURCE-REGISTRY-DIRECTIVE > ; ASDF::VALIDATE-SOURCE-REGISTRY-FORM > ; ASDF::VALIDATE-SOURCE-REGISTRY-FILE > ; ASDF::VALIDATE-SOURCE-REGISTRY-DIRECTORY > ; ASDF::PARSE-SOURCE-REGISTRY-STRING > ; ASDF::REGISTER-ASD-DIRECTORY > ; (DEFPARAMETER ASDF:*DEFAULT-SOURCE-REGISTRIES*) > ; (DEFPARAMETER ASDF::*SOURCE-REGISTRY-FILE*) > ; (DEFPARAMETER ASDF::*SOURCE-REGISTRY-DIRECTORY*) > ; ASDF::WRAPPING-SOURCE-REGISTRY > ; ASDF::DEFAULT-SOURCE-REGISTRY > ; ASDF::USER-SOURCE-REGISTRY > ; ASDF::SYSTEM-SOURCE-REGISTRY > ; ASDF::USER-SOURCE-REGISTRY-DIRECTORY > ; ASDF::SYSTEM-SOURCE-REGISTRY-DIRECTORY > ; ASDF::ENVIRONMENT-SOURCE-REGISTRY > ; (DEFGENERIC ASDF:PROCESS-SOURCE-REGISTRY) > ; (METHOD ASDF:PROCESS-SOURCE-REGISTRY (SYMBOL)) > ; (METHOD ASDF:PROCESS-SOURCE-REGISTRY (PATHNAME)) > ; (METHOD ASDF:PROCESS-SOURCE-REGISTRY (STRING)) > ; (METHOD ASDF:PROCESS-SOURCE-REGISTRY (NULL)) > ; (METHOD ASDF:PROCESS-SOURCE-REGISTRY (CONS)) > ; ASDF::INHERIT-SOURCE-REGISTRY > ; ASDF::PROCESS-SOURCE-REGISTRY-DIRECTIVE > ; ASDF:COMPUTE-SOURCE-REGISTRY > ; ASDF:INITIALIZE-SOURCE-REGISTRY > ; ASDF:ENSURE-SOURCE-REGISTRY > ; (TOP-LEVEL-FORM 285) > ; (TOP-LEVEL-FORM 286) > ; (TOP-LEVEL-FORM 287) > ;; Processing Cross Reference InformationASDF compiled cleanly > Error: The variable CODE is unbound. > 1 (continue) Try evaluating CODE again. > 2 Return the value of :CODE instead. > 3 Specify a value to use this time instead of evaluating CODE. > 4 Specify a value to set CODE to. > 5 Try loading test/compile-asdf.lisp again. > 6 Give up loading test/compile-asdf.lisp. > 7 Try loading another file instead of test/compile-asdf.lisp. > 8 (abort) Abort initialization. > 9 Continue to top-level loop. > Type :b for backtrace or :c <option number> to proceed. > Type :bug-form "<subject>" for a bug report template or :? for other > options. > CL-USER 1 : 1 > > > On Feb 27, 2010, at 19:13 PM, Faré wrote: > > Please > 1- use the latest ASDF from git > 2- have a symlink to lwm64 in your PATH named lispworks > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org > ] > The Slogan of "Language Independence" is often but the pride that > self-ignorant > monolinguists put in not calling "language" the collection of barkings and > grunts they invent to interact with their computers. — Faré > > > > > On 27 February 2010 21:03, David McClain <dbm(a)refined-audiometrics.com> > wrote: > > Ahh yes, of course.. However, when I try the command line: > > bash-3.2$ test/run-tests.sh lispworks > > test/run-tests.sh: line 162: type: lispworks: not found > > test/run-tests.sh: line 57: (load "test/compile-asdf.lisp"): No such file or > > directory > > bash-3.2$ > > So here is the script... what am I, or have I done incorrectly? > > > Dr. David McClain > dbm(a)refined-audiometrics.com > > >

2 1

Re: [asdf-devel] ASDF testing
by Robert Goldman 28 Feb '10

28 Feb '10

On 2/27/10 Feb 27 -8:16 AM, David McClain wrote: > Hello Robert, > > I took a look at your test shell script (run-tests.sh) and made the > adjustment for running my saved image named lwm64. > > After some tests I found that the Lisp image has its working directory > set to the same directory from which you start it, and indeed there is a > command line arg -eval to allow the evaluation of an initial form. > > However, even after several attempts at quoting the initial command > '(load "test/compile-asdf.lisp")', I cannot get it past Bash to send it > to the Lisp image. Sorry for being so lame on shell scripting -- it has > been many years since I was deep into them. No need to apologize to me. I'm an unregenerate T shell user, so my understanding of these scripts is pretty much at the Cargo Cult level. > The error I keep getting is: > > bash-3.2$ test/run-tests.sh lwm64 > > test/run-tests.sh: line 57: (load "test/compile-asdf.lisp"): No such > file or directory It looks to me as if the argument we are passing to the LW runtime is being interpreted as a file to load, not an s-expression to be evaluated. Does that sound right to you? E.g., in ACL, we start this up as something like alisp -e '(load "test/compile-asdf.lisp")' and for SBCL sbcl --eval '(load "test/compile-asdf.lisp")' Is there some equivalent to -e/--eval that works for lispworks? Their documentation seems relatively unfriendly to text-mode folks like me; seems very focused on the IDE. > > And when I quote it variously, the same message appears with my quoting > intact. > > So, since you only want to execute that simple command in Lisp, here is > the resulting output after I enter it manually: > .... > ;; Processing Cross Reference InformationASDF compiled cleanly > Error: The variable CODE is unbound. > 1 (continue) Try evaluating CODE again. > 2 Return the value of :CODE instead. > 3 Specify a value to use this time instead of evaluating CODE. > 4 Specify a value to set CODE to. > 5 Try loading test/compile-asdf.lisp again. > 6 Give up loading test/compile-asdf.lisp. > 7 Try loading another file instead of test/compile-asdf.lisp. > 8 (abort) Return to level 0. > 9 Return to top-level loop. > 10 Return from multiprocessing. > > Type :b for backtrace or :c <option number> to proceed. > Type :bug-form "<subject>" for a bug report template or :? for other > options. > It looks to me as if compile-asdf is running to completion, through the cond expression in that file (hence the "ASDF compiled cleanly"), and then something is failing. The Processing Cross Reference string there suggests that it might be something the LW IDE is doing, but I can't guess what that would be. Maybe someone else on the list can suggest something.... best, r

3 10

[asdf-devel] ASDF testing
by Robert Goldman 26 Feb '10

26 Feb '10

Any chance you could run the ASDF tests (with run-tests.sh) on Lispworks? If you'd be willing to do this, feel free to call on me for any assistance. I can't figure out how to run this with my personal edition: as far as I can tell, one needs to use save-image to create an image that can be used for script execution, and save-image is not available in the personal edition. So I don't believe I can simply run lw from the command-line (nor do I know its command-line arguments). best, r

1 0

[asdf-devel] Changes to ASDF for LW6
by David McClain 26 Feb '10

26 Feb '10

Hi, I just installed the latest available source for ASDF and had to make a few minor changes to the way the ASDF Package was being defined, for compatibility with Lispworks 6.0: (changes highlighted in red -- if you can see them) ... (ensure-shadow (package symbols) (shadow symbols package)) (ensure-package (name &key nicknames use export unintern shadow) (let* ((p (ensure-exists name nicknames))) (ensure-use p use) (ensure-unintern p unintern) (ensure-shadow p shadow) (ensure-export p export) p))) (ensure-package ':asdf-utilities :nicknames '(#:asdf-extensions) :use '(#:common-lisp) :export '(#:absolute-pathname-p #:aif #-:LISPWORKS #:appendf #:asdf-message #:coerce-name #:directory-pathname-p #:ends-with #:ensure-directory-pathname #-:LISPWORKS #:getenv #:get-uid #:length=n-p #:make-collector #:pathname-directory-pathname #:pathname-sans-name+type ;; deprecated. Use pathname-directory-pathname #:read-file-forms #:remove-keys #:remove-keyword #:resolve-symlinks #:split #:component-name-to-pathname-components #:system-registered-p #:truenamize)) (ensure-package ':asdf :use '(:common-lisp :asdf-utilities) :unintern '(#:*asdf-revision*) :shadow #+:LISPWORKS '(#:load-system #:compile-system #:defsystem) #-:LISPWORKS '() :export '(#:defsystem #:oos #:operate #:find-system #:run-shell-command #:system-definition-pathname #:find-component ; miscellaneous #:compile-system #:load-system #:test-system #:compile-op #:load-op #:load-source-op Dr. David McClain dbm(a)refined-audiometrics.com

5 26

[asdf-devel] Oh yes...
by David McClain 26 Feb '10

26 Feb '10

Hi, Oh yes, I also commented out the definitions for APPENDF and GET-ENV: #-:LISPWORKS (define-modify-macro appendf (&rest args) append "Append onto list") #-:LISPWORKS (defun getenv (x) #+sbcl (sb-ext:posix-getenv x) #+clozure (ccl::getenv x) #+clisp (ext:getenv x) #+cmu (cdr (assoc (intern x :keyword) ext:*environment-list*)) #+lispworks (lispworks:environment-variable x) #+allegro (sys:getenv x) #+gcl (system:getenv x) #+ecl (si:getenv x)) Dr. David McClain dbm(a)refined-audiometrics.com

1 0

[asdf-devel] [PATCH] add &allow-other-keys to LOAD-SYSTEM, COMPILE-SYSTEM, TEST-SYSTEM
by Tobias C. Rittweiler 24 Feb '10

24 Feb '10

Although the way to extend operations by additional initargs is somewhat cumbersome, it's possible. Unfortunately, the sugar forms LOAD-SYSTEM, COMPILE-SYSTEM, and TEST-SYSTEM do not take additional initargs. -T. diff --git a/asdf.lisp b/asdf.lisp index 92e7f6e..3f230d5 100644 --- a/asdf.lisp +++ b/asdf.lisp @@ -1670,18 +1670,24 @@ created with the same initargs as the original one. (setf (documentation 'operate 'function) operate-docstring)) -(defun load-system (system &rest args &key force (verbose t) version) - "Shorthand for `(operate 'asdf:load-op system)`. See [operate][] for details." +(defun load-system (system &rest args &key force (verbose t) version + &allow-other-keys) + "Shorthand for `(operate 'asdf:load-op system)`. See [operate][] for +details." (declare (ignore force verbose version)) (apply #'operate 'load-op system args)) -(defun compile-system (system &rest args &key force (verbose t) version) - "Shorthand for `(operate 'asdf:compile-op system)`. See [operate][] for details." +(defun compile-system (system &rest args &key force (verbose t) version + &allow-other-keys) + "Shorthand for `(operate 'asdf:compile-op system)`. See [operate][] +for details." (declare (ignore force verbose version)) (apply #'operate 'compile-op system args)) -(defun test-system (system &rest args &key force (verbose t) version) - "Shorthand for `(operate 'asdf:test-op system)`. See [operate][] for details." +(defun test-system (system &rest args &key force (verbose t) version + &allow-other-keys) + "Shorthand for `(operate 'asdf:test-op system)`. See [operate][] for +details." (declare (ignore force verbose version)) (apply #'operate 'test-op system args))

3 10

[asdf-devel] upgradability with ECL
by Tobias C. Rittweiler 24 Feb '10

24 Feb '10

Current ECL HEAD comes with asdf version "1.604", but trying to load upstreams asdf.lisp won't work because of "A package with the name ASDF-EXTENSIONS already exists." Indeed, CLHS DEFPACKAGE says If one of the supplied :nicknames already refers to an existing package, an error of type package-error is signaled. In fact, using DEFPACKAGE for upgradability purposes is ill-conceived from the beginning because of: If defined-package-name already refers to an existing package, the name-to-package mapping for that name is not changed. If the new definition is at variance with the current state of that package, the consequences are undefined; ... And, e.g. the :EXPORT list changed in numerous points in past, and is not excluded from changing in the future. The portable venue would be not to use DEFPACKAGE but either to define a DEFINE-PACKAGE macro on top of the functional layer yourself, or using the functional layer directly. Mwahaha. Suckage. :-) -T.

4 4

[asdf-devel] default source registry...
by Faré 22 Feb '10

22 Feb '10

Should we base our search path on the XDG Base Directory Specification? http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html To the point of actually using getenv to get these search paths? I say we should. The default configuration files should be $XDG_CONFIG_DIRS/common-lisp/source-registry.conf $XDG_CONFIG_DIRS/common-lisp/source-registry.conf.d/ And the default search path should include $XDG_DATA_DIRS/common-lisp/systems/ $XDG_DATA_DIRS/common-lisp/source// The default cache path should be under $XDG_CACHE_HOME/common-lisp/ Unless anyone objects, I'll implement that behavior and commit something like ASDF 1.695. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Vision is the art of seeing what is invisible to others. — Jonathan Swift

4 4

[asdf-devel] patch for component-relative-pathname
by james anderson 22 Feb '10

22 Feb '10

good morning; if a system definition root pathname contains a logical host, component-relative-pathname fails to produce pathnames which are relative in the sense that the combination with their parent's component pathname produces the intended location. this patch corrects that failing for sbcl and ccl. (defmethod component-relative-pathname ((component source-file)) (let ((*default-pathname-defaults* (component-pathname (component-parent component)))) (merge-component-relative-pathname (slot-value component 'relative-pathname) (component-name component) (source-file-type component (component-system component))))) attached below are descriptions of the respective data which illustrate the problem. in sbcl, when the result "relative" pathname is merged with that of the parent, the physical pathname host shadows the logical host. in ccl, the defaulting logic for make-pathname asserts an absolute root directory path in the "relative" pathname. sbcl: ------- 0] (rest (asdf::system-registered-p :de.setf.amqp)) #<ASDF:SYSTEM "de.setf.amqp" {11D56469}> 0] (describe *) #<ASDF:SYSTEM "de.setf.amqp" {11D56469}> [standard-object] Slots with :INSTANCE allocation: NAME = "de.setf.amqp" VERSION = "20100214-0.3" IN-ORDER-TO = ((ASDF:LOAD-OP.. DO-FIRST = ((ASDF:COMPILE-OP.. INLINE-METHODS = NIL PARENT = NIL RELATIVE-PATHNAME = #P"AMQP:" OPERATION-TIMES = #<HASH-TABLE :TEST EQL :COUNT 0 {11D9C791}> PROPERTIES = ((ASDF:SYSTEM-NICKNAMES :SETF.AMQP).. COMPONENTS = (#<ASDF:CL-SOURCE-FILE "package" {11DC6E11}>.. IF-COMPONENT-DEP-FAILS = :FAIL DEFAULT-COMPONENT-CLASS = NIL DESCRIPTION = "An AMQP client library" LONG-DESCRIPTION = "`de.setf.amqp` implements a native Common Lisp client library for the.. AUTHOR = #<unbound slot> MAINTAINER = #<unbound slot> LICENCE = #<unbound slot> SOURCE-FILE = #P"/Development/Source/dev/Library/de/ setf/amqp/amqp.asd" 0] (rest (asdf::system-registered-p :de.setf.utility)) #<ASDF:SYSTEM "de.setf.utility" {11D9C2B9}> 0] (describe *) #<ASDF:SYSTEM "de.setf.utility" {11D9C2B9}> [standard-object] Slots with :INSTANCE allocation: NAME = "de.setf.utility" VERSION = "20100214-1.0" IN-ORDER-TO = NIL DO-FIRST = ((ASDF:COMPILE-OP (ASDF:LOAD-OP))) INLINE-METHODS = NIL PARENT = NIL RELATIVE-PATHNAME = #P"LIBRARY:DE;SETF;UTILITY;" OPERATION-TIMES = #<HASH-TABLE :TEST EQL :COUNT 0 {11DEACB9}> PROPERTIES = ((ASDF:SYSTEM-NICKNAMES "de.setf.utility")) COMPONENTS = (#<ASDF:CL-SOURCE-FILE "package" {11D9C8D9}>.. IF-COMPONENT-DEP-FAILS = :FAIL DEFAULT-COMPONENT-CLASS = NIL DESCRIPTION = #<unbound slot> LONG-DESCRIPTION = #<unbound slot> AUTHOR = #<unbound slot> MAINTAINER = #<unbound slot> LICENCE = #<unbound slot> SOURCE-FILE = #P"/Development/Source/dev/Library/de/ setf/utility/utility.asd" 0] (first (asdf::module-components (rest (asdf::system-registered- p :de.setf.utility)))) #<ASDF:CL-SOURCE-FILE "package" {11D9C8D9}> 0] (describe *) #<ASDF:CL-SOURCE-FILE "package" {11D9C8D9}> [standard-object] Slots with :INSTANCE allocation: NAME = "package" VERSION = #<unbound slot> IN-ORDER-TO = NIL DO-FIRST = ((ASDF:COMPILE-OP (ASDF:LOAD-OP))) INLINE-METHODS = NIL PARENT = #<ASDF:SYSTEM "de.setf.utility" {11D9C2B9}> RELATIVE-PATHNAME = NIL OPERATION-TIMES = #<HASH-TABLE :TEST EQL :COUNT 0 {11DEC591}> PROPERTIES = NIL 0] (describe (asdf::component-relative-pathname (first (asdf::module- components (rest (asdf::system-registered-p :de.setf.utility)))))) #P"package.lisp" [structure-object] Slots with :INSTANCE allocation: HOST = #<SB-IMPL::UNIX-HOST {102CE661}> DEVICE = NIL DIRECTORY = (:RELATIVE) NAME = "package" TYPE = "lisp" VERSION = :NEWEST 0] (type-of (asdf::component-relative-pathname (first (asdf::module- components (rest (asdf::system-registered-p :de.setf.utility)))))) PATHNAME 0] ; ------- ccl: ------ > Error: File #P"LIBRARY:package.lisp.newest" not found > While executing: CCL::FCOMP-FIND-FILE, in process listener(1). > Type :GO to continue, :POP to abort, :R for a list of available restarts. > If continued: Skip evaluation of (asdf:operate 'asdf:load- op :de.setf.amqp.amqp-1-1-0-8-0) > Type :? for other options. 1 > (describe (rest (asdf::system-registered-p :de.setf.utility))) #<SYSTEM "de.setf.utility" #x878732E> Class: #<STANDARD-CLASS ASDF:SYSTEM> Wrapper: #<CCL::CLASS-WRAPPER ASDF:SYSTEM #x86085FE> Instance slots ASDF::NAME: "de.setf.utility" ASDF:VERSION: "20100214-1.0" ASDF::IN-ORDER-TO: NIL ASDF::DO-FIRST: ((ASDF:COMPILE-OP (ASDF:LOAD-OP))) ASDF::INLINE-METHODS: NIL ASDF::PARENT: NIL ASDF::RELATIVE-PATHNAME: #P"LIBRARY:de;setf;utility;" ASDF::OPERATION-TIMES: #<HASH-TABLE :TEST EQL size 0/60 #x878702E> ASDF::PROPERTIES: ((ASDF:SYSTEM-NICKNAMES "de.setf.utility")) ASDF::COMPONENTS: (#<CL-SOURCE-FILE "package" #x8786E86> #<CL-SOURCE-FILE "pathnames" #x8786B1E> #<CL-SOURCE-FILE "modpackage" #x878675E> #<MODULE "documentation" #x878637E> #<CL-SOURCE-FILE "string" #x87857FE> #<CL-SOURCE-FILE "conditions" #x87853F6> #<MODULE "clos" #x8784FCE> #<MODULE "test" #x87847EE> #<CL-SOURCE-FILE "date" #x8783C56> #<CL-SOURCE-FILE "list" #x87837EE>) ASDF::IF-COMPONENT-DEP-FAILS: :FAIL ASDF::DEFAULT-COMPONENT-CLASS: NIL ASDF::DESCRIPTION: #<Unbound> ASDF::LONG-DESCRIPTION: #<Unbound> ASDF::AUTHOR: #<Unbound> ASDF::MAINTAINER: #<Unbound> ASDF::LICENCE: #<Unbound> ASDF:SOURCE-FILE: #P"/Development/Source/dev/Library/de/setf/utility/ utility.asd" 1 > (describe (first (asdf::module-components (rest (asdf::system- registered-p :de.setf.utility))))) #<CL-SOURCE-FILE "package" #x8786E86> Class: #<STANDARD-CLASS ASDF:CL-SOURCE-FILE> Wrapper: #<CCL::CLASS-WRAPPER ASDF:CL-SOURCE-FILE #x8643A8E> Instance slots ASDF::NAME: "package" ASDF:VERSION: #<Unbound> ASDF::IN-ORDER-TO: NIL ASDF::DO-FIRST: ((ASDF:COMPILE-OP (ASDF:LOAD-OP))) ASDF::INLINE-METHODS: NIL ASDF::PARENT: #<SYSTEM "de.setf.utility" #x878732E> ASDF::RELATIVE-PATHNAME: NIL ASDF::OPERATION-TIMES: #<HASH-TABLE :TEST EQL size 0/60 #x8786B86> ASDF::PROPERTIES: NIL 1 > (describe (asdf::component-relative-pathname (first (asdf::module- components (rest (asdf::system-registered-p :de.setf.utility)))))) #P"LIBRARY:package.lisp.newest" Type: LOGICAL-PATHNAME Class: #<BUILT-IN-CLASS LOGICAL-PATHNAME> TYPE: (LOGICAL-PATHNAME . #<CCL::CLASS-WRAPPER LOGICAL-PATHNAME #x809E75E>) 1: (:ABSOLUTE) 2: "package" 3: "lisp" %LOGICAL-PATHNAME-HOST: "LIBRARY" %LOGICAL-PATHNAME-VERSION: :NEWEST 1 > (in-package :asdf) #<Package "ASDF"> 1 > (defmethod component-relative-pathname ((component source-file)) (let ((*default-pathname-defaults* (make-pathname :name nil :type nil :directory nil :host nil :defaults (component-pathname (component- parent component))))) (merge-component-relative-pathname (slot-value component 'relative-pathname) (component-name component) (source-file-type component (component-system component))))) #<STANDARD-METHOD COMPONENT-RELATIVE-PATHNAME (SOURCE-FILE)> 1 > (describe (asdf::component-relative-pathname (first (asdf::module- components (rest (asdf::system-registered-p :de.setf.utility)))))) #P"package.lisp" Type: PATHNAME Class: #<BUILT-IN-CLASS PATHNAME> TYPE: (PATHNAME . #<CCL::CLASS-WRAPPER PATHNAME #x80A0F16>) %PATHNAME-DIRECTORY: (:RELATIVE) %PATHNAME-NAME: "package" %PATHNAME-TYPE: "lisp" %PHYSICAL-PATHNAME-VERSION: :NEWEST %PHYSICAL-PATHNAME-DEVICE: NIL 1 >

3 21

[asdf-devel] Q on compiling ASDF
by Daniel Herring 22 Feb '10

22 Feb '10

Apparently the ASDF-binary-locations (now asdf-output-locations) code originated from Slime. In Slime, this code allowed a simple loader to put incompatible fasls in separate paths. Now that ABL (AOL) is a standard part of ASDF, what is the proper way to bootstrap/write a (load (compile-file "asdf.lisp")) and have the fasls appear in implementation-specific directories? I ask this in relation to Nick's problem on Lispworks. Though I suspect a few extra stack frames (close to the patch I reported for clisp) are to blame for his immediate problem, in principle it would be good to always load the compiled form. Thanks, Daniel

3 2

[asdf-devel] Module-depends patch is in place
by Robert Goldman 14 Feb '10

14 Feb '10

OK, I have merged the module-depends branch into master and pushed the result. I suppose we should probably kill the module-depends branch on the public repo now.... Have a good weekend, all! r

2 2

[asdf-devel] minor suggestions
by Tobias C. Rittweiler 14 Feb '10

14 Feb '10

* How about adding a TEST-OP to ASDF's asd? * (asdf::version-satisfies (asdf:asdf-version) (asdf:asdf-version)) may be a trivial test case for version-satisfies. It's not obvious how to add test cases. -T.

3 2

[asdf-devel] Trying again
by Robert Goldman 12 Feb '10

12 Feb '10

OK, I have just pushed an alternative solution to the module dependency bug, this one (I believe) only triggered by INTRA-system dependencies. This one is also on the module-depends branch. This was achieved, as I said, at the cost of some hair, but I believe it does the right thing to the extent that I understand the right thing, and thinking about James's email convinced me that I /don't/ understand what is the right thing with respect to inter-system dependencies. Somewhat disappointingly, this commit agrees with the last one on the tests, which indicates that the tests need to be augmented... Additional reviews very welcome as are test results! [Fare: is your XCVB going to handle the kinds of inter-system issues I raised in my earlier email?] Feeling like Richard III, I can only say "A spec! A spec! My kingdom for a spec!" Cheers, r

3 14

[asdf-devel] Module dependencies still arguably wrong
by Robert Goldman 11 Feb '10

11 Feb '10

Earlier I claimed that the new ASDF TRAVERSE computed a conservative approximation to what needed to be recompiled. In particular, if we have (defsystem X :depends-on (Y) ....) With the new patch, if we do load-op on X, and Y has changed, X will be recompiled. In Classic ASDF, this would not happen. However, even with the new patch, this does not happen correctly. In particular, this case will not work properly (defsystem X :depends-on (Y) ...) (defsystem Z :depends-on (Y) ...) Let's imagine I load X and Z, which causes me to load Y. Now I modify some of the code of Y and reload X. ASDF will notice the change in Y and trigger a recompilation of X. BUT if I now (asdf:load-system :z), when we check the dependencies of Z and find Y, there will be nothing that needs to be done for Y, so recompilation of Z will /not/ be triggered. So the problem with trying to do a conservative estimation of what needs to be recompiled is that we don't store with a system object information about the state of things upon which it depends, so we cannot detect a change in the state of those dependencies..... Information about the last compilation of a system /is/ available in ASDF, but we don't store with X and Z information about the state of Z when they were compiled. To open YA can of worms, we also don't cache information about systems *across lisp sessions*. But I think I'll just raise that issue and then drop it like a hot potato. Cheers, r

2 2

[asdf-devel] asdf.x [was : Launchpad bug 502946
by james anderson 11 Feb '10

11 Feb '10

good morning; as is evident from the message attached below, for the past several days i have thought about things related to bug-502946, and asdf in general. my state-of-mind as of last week was, for the reasons alluded to below, that it is not productive to try to reason about system construction issues in the concrete context of asdf, -1.502, as it was at the time. i do not refer to with matters of configuration, or pathname mapping, or even 'elegant' bootstrapping, but rather to the need for a platform on which to think about and implement tools to - manage systems with articulated interfaces - manipulate system definitions programmatically - automate system definition construction and maintenance the larger concerns for integration with production, build, and deployment systems do all matter, just not right now. if one would set out the tasks in more detail, one could think about how to approach the issues, but at present, it is difficult to think even just about how asdf works. the only reasonable approach was to take asdf apart, isolate the functional components and reassemble them in a manner which allows to think about how a tool to manage program components works and how it might work. the current state is captured in de.setf.asdf.x[1]. there is a readme[2], which describes the intent, and the asdf-x.lisp[3] file, which reimplements asdf.lisp. there is also a unit test[4] which captures one interpretation of the 'strongly-dependent' requirement relation. on one hand, as a radical rational reconstruction of the original, it does not contribute to the main stream. on the other, the result provides the terms to think about what "intra-system" dependency is and a concrete context in which to implement projective proposals. cf. the commit[5] to support strong dependency by adding a state variable to the constraint machinery and adding the declaration to control it to the system definition language. most of which took the form of additional methods. --- [1]: http://github.com/lisp/de.setf.asdf.x [2]: http://github.com/lisp/de.setf.asdf.x/blob/master/README.md [3]: http://github.com/lisp/de.setf.asdf.x/blob/master/asdf-x.lisp [4]: http://github.com/lisp/de.setf.asdf.x/blob/master/test/launchpad/ bug-502946.lisp [5]: http://github.com/lisp/de.setf.asdf.x/commit/ 285a38e4ee18e10b5ce887d8ab2dd5e2d352aa0a Begin forwarded message: > From: james anderson <james.anderson(a)setf.de> > Date: 2010-02-07 23:45:56GMT+01:00 > To: rpgoldman(a)sift.info > Subject: Re: [asdf-devel] Launchpad bug 502946 > > good evening; > > you may, or may not be expecting this, but i got tired of trying to > understand traverse. > and tired of trying to understand parse-component, and defsystem, > and pathname resolution, and ... > i am now about 3/4 through rewriting asdf with clear protocols for > - definition operators (at all three levels - system, module, element) > - perform - with distinct qualifiers for requirement (dependency, > constituency) traversal, restart > - requirement and constituency specification canonicalization > - status evaluation for completion, features, other arbitrary > predicates > - settings/environment assertions per component > - pathname resolution which does not depend on the quirks of > *default-pathname-defaults* > > it's about the same amount of code - even though many of the > internal operators are decomposed to make the mechanism explicit. > > the most unsettling part is to ensure that - between the bnf in the > docs and the logic of the code, i've gotten the dependency > definitions right, but it won't be long. i've been chewing through > this since friday, so maybe by the time you're up tomorrow, there > will be some code up in github which passes the tests. the intent > is plug-compatible for the things i can understand, and i'm putting > it in a new package, so with a couple package-name swaps, one can > try things side-by-side. i will let you know. > > > On 2010-02-07, at 22:40 , Robert Goldman wrote: > >> Wrt https://bugs.launchpad.net/asdf/+bug/502946, >> module is not recompiled if _intra_-system dependency changes, I have >> spent quite some time groveling over the source code to TRAVERSE, >> and I >> believe that this is going to be quite difficult to fix. There are a >> number of assumptions baked into TRAVERSE, and some complicated >> uses of >> a variable scoped over the body of TRAVERSE, together with a >> number of >> local functions and a soupcon of unstated assumptions. >> >> I'm pretty sure that modules are substantially broken and, in the >> short >> term, I would discourage ASDF system designers from using them at >> all. >> >> I have been banging my head on this for at least a working day's >> worth >> of hours, and I need someone with whom to discuss the code, either by >> voice, IM or IRC. Email is not going to be high enough bandwidth. >> >> If anyone is interested in this enough to share the pain with me, >> please >> drop me a line and we can coordinate. >> >> Thanks, >> r >> >> _______________________________________________ >> asdf-devel mailing list >> asdf-devel(a)common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel >

1 0

[asdf-devel] last note about the module dependencies for now...
by Robert Goldman 10 Feb '10

10 Feb '10

I believe by adding a little bit more hair (a test that a component IS a module and IS NOT a system) to the TRAVERSE structure, I can salvage INTRA-system dependencies involving modules without trying to fix INTER-system dependencies, which seems like too big a bite to chew off. What would people think about that? I'm afraid, pace James A, that this won't make the code a lot simpler or more elegant, but it will make the behavior more predictable, which is a Good Thing. This exhibits a Common Lisp hassle pattern I have written myself into far too often --- you make a class (in this case system) inherit from another class (in this case module), and later on find that you should have built a triangular relationship between module, system and a common superclass. Introducing that common superclass is often quite painful.... In this case, I think backward compatibility rules out this kind of refactoring (impossible to tell whose system subclasses you might break), so the best we can do is put on some inelegant band-aids like (when (and (typep x 'module) (not (typep x 'system)) ....) cheers, r

1 0

[asdf-devel] New module-depends branch contents pushed
by Robert Goldman 10 Feb '10

10 Feb '10

Not a fast-forward push. But should be well worth it! Best, r

2 2

[asdf-devel] Refined the module dependency fix
by Robert Goldman 10 Feb '10

10 Feb '10

I have a series of patches I am about to push to the module-depends branch. Because I have had to rebase this onto master as new master changes have come in, this will not be a fast-forward update when you pull it into your local repo. So this is a head's up. I will push the update sometime after lunchtime my time (US Central time). Question: is anyone trying this out? Anyone have a good criterion for when I should close this branch out and merge it into master? Best, Robert

1 0

[asdf-devel] Looking for some help crafting a test case
by Robert Goldman 10 Feb '10

10 Feb '10

I believe my first ASDF patch had a minor buglet that could cause over-compilation. Here's the deal: when new TRAVERSE detects that the components of a module need to have an operation performed on them, it binds a dynamic variable and calls itself on the components of the module. The dynamic variable forces the components to be done even when they satisfy operation-done-p. This has an effect equivalent to propagating the module's dependencies onto the children. However, this also means that the dynamic variable is in place when we call TRAVERSE recursively on the dependencies recorded on the children, then those dependencies are forced to happen as well. In /theory/ this could cause over-compilation, over-loading, etc. However, I cannot come up with a test case where this will /actually/ occur. Why is that? It's because components of modules cannot "reach out" of the containing module to depend on anything in their surroundings. E.g. if I have a module FOO, then components of FOO can record dependencies only onto other components of FOO. This is a consequence of how name resolution works in ASDF. So I have what I think is a fix for performing unnecessary operations in ASDF, but I cannot figure out a way to craft a test case where unnecessary operations could actually occur. I feel like I should put the patch in anyway, in case we change the rules on name-lookup in ASDF, but this feels wrong. Any suggestions? Have I missed something? Is there any way, for example, a component of FOO could depend on an outside system? I don't believe that this is possible, but I could be wrong. thanks, r

2 1

[asdf-devel] clisp getuid
by Pascal Bourguignon 08 Feb '10

08 Feb '10

In asdf.lisp downloaded from the web page this afternoon, line 500. With clisp, the package LINUX is available only in special circumstances. (it has to run on Linux, AND the glibc bindings module must have been compiled AND clisp must have been launched with it, usually with -Kfull). So when using the LINUX package on clisp, we must test for it explicitely: #+(and clisp #.(cl:if (cl:find-package "LINUX") '(:and) '(:or))) (defun get-uid () (linux:getuid)) A better alternative is to use POSIX:UID, which is available on a wider range of systems (IIRC, MS-Windows is POSIX too): #+clisp (defun get-uid () (POSIX:UID)) (and similarly for the PID if needed, (POSIX:PROCESS-ID)) -- __Pascal Bourguignon__

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel February 2010