asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

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 13 Feb '10

13 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel