asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] Released ASDF 1.372
by Faré 09 Dec '09

09 Dec '09

Having had no feedback for a week, and passing tests, I decided I'd push what I have so far to the official repository. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]

1 0

[asdf-devel] Bizarre consequences of FIND-SYSTEM in ASDF.
by Samium Gromoff 02 Dec '09

02 Dec '09

This appears to happen both on 1.369 and whatever is shipped with fresh SBCL. Prerequisites: ensure a setup where both MCCLIM and CL-UTILITIES are loadable after ASDF is loaded. root@auriga:/home/deepfire/source# sbcl --eval '(require :asdf)' --eval '(asdf:find-system :mcclim)' This is SBCL 1.0.33.2, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * (defun asdf-hidden-system-names (name) "Find out names of ASDF systems hiding in system going by NAME. A hidden system is a system with a definition residing in a file named differently from that system's name. Warning: demo-only, trimmed-down version." (let ((asdf::*defined-systems* (make-hash-table :test 'equalp))) (handler-case (let ((*break-on-signals* nil)) (format t "about to find system ~A~%" name) (let ((system (asdf:find-system name))) (format t "finding system ~A: ~A, ~S~%" name system (asdf:system-definition-pathname system)))) (error (c) (format t "~@<; ~@;WARNING: error while querying ASDF about hidden names of system ~S: ~A~:@>~%" name c))) (hash-table-count asdf::*defined-systems*))) ASDF-HIDDEN-SYSTEM-NAMES * (asdf-hidden-system-names :cl-utilities) about to find system CL-UTILITIES ; loading system definition from /root/.sbcl/systems/esa-mcclim.asd into ; #<PACKAGE "ASDF1"> ; registering #<SYSTEM :CLIM-LISP {1003773701}> as CLIM-LISP ; registering #<SYSTEM :CLIM-BASIC {10037D4331}> as CLIM-BASIC ; registering #<SYSTEM :GOATEE-CORE {10038425B1}> as GOATEE-CORE ; registering #<SYSTEM :CLIM-POSTSCRIPT {10038A3601}> as CLIM-POSTSCRIPT ; registering #<SYSTEM :CLIM-CORE {1003904611}> as CLIM-CORE ; registering #<SYSTEM :ESA-MCCLIM {100396A641}> as ESA-MCCLIM ; loading system definition from /root/.sbcl/systems/swank.asd into ; #<PACKAGE "ASDF2"> ; registering #<SYSTEM :SWANK {1003A6F6F1}> as SWANK ; registering #<SYSTEM :DREI-MCCLIM {1002F89911}> as DREI-MCCLIM ; registering #<SYSTEM :DREI-TESTS {1003004691}> as DREI-TESTS ; registering #<SYSTEM :CLIM {100306A641}> as CLIM ; registering #<SYSTEM :CLIM-CLX {10030C5591}> as CLIM-CLX ; registering #<SYSTEM :CLIM-BEAGLE {1003129621}> as CLIM-BEAGLE ; registering #<SYSTEM :CLIM-NULL {100319F5A1}> as CLIM-NULL ; registering #<SYSTEM :CLIM-GTKAIRO {10031FD5B1}> as CLIM-GTKAIRO ; registering #<SYSTEM :CLIM-GRAPHIC-FORMS {1003261AE1}> as CLIM-GRAPHIC-FORMS ; registering #<SYSTEM :CLIM-OPENGL {10032C6631}> as CLIM-OPENGL ; registering #<SYSTEM :CLIM-LOOKS {1003322B11}> as CLIM-LOOKS ; registering #<SYSTEM :MCCLIM {1003388291}> as MCCLIM finding system CL-UTILITIES: #<SYSTEM "cl-utilities" {1002C5F2F1}>, #P"/root/.sbcl/systems/cl-utilities.asd" 20 * What happens here is that cl-utilities.asd imperatively requires sb-rotate-byte from within its supposedly declarative sysdef, loading of which, through some inexplicable twist of events, causes lookups of seemingly unrelated software. A backtrace which reveals somewhat more of what's going on: 1: (FIND-SYSTEM "esa-mcclim" NIL) 2: ((SB-PCL::FAST-METHOD FIND-COMPONENT ((EQL NIL) T)) #<unused argument> #<unused argument> #<unused argument> "esa-mcclim" NIL) 3: (ASDF::PARSE-COMPONENT-FORM NIL (:MODULE "esa-mcclim" :PATHNAME #P"/little/home/empty/desr/git/mcclim/" :DEPENDS-ON (:CLIM-CORE) :COMPONENTS ((:MODULE "ESA" :COMPONENTS ((:FILE "packages") (:FILE "utils" :DEPENDS-ON #) (:FILE "colors" :DEPENDS-ON #) (:FILE "esa" :DEPENDS-ON #) (:FILE "esa-buffer" :DEPENDS-ON #) (:FILE "esa-io" :DEPENDS-ON #) (:FILE "esa-command-parser" :DEPENDS-ON #)))))) 4: (SB-INT:SIMPLE-EVAL-IN-LEXENV (ASDF::PARSE-COMPONENT-FORM NIL (APPLY #'LIST :MODULE (ASDF::COERCE-NAME ':ESA-MCCLIM) :PATHNAME #P"/little/home/empty/desr/git/mcclim/" '(:DEPENDS-ON (:CLIM-CORE) :COMPONENTS ((:MODULE "ESA" :COMPONENTS #))))) #<NULL-LEXENV>) 5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (DEFSYSTEM :ESA-MCCLIM :DEPENDS-ON (:CLIM-CORE) :COMPONENTS ((:MODULE "ESA" :COMPONENTS ((:FILE "packages") (:FILE "utils" :DEPENDS-ON #) (:FILE "colors" :DEPENDS-ON #) (:FILE "esa" :DEPENDS-ON #) (:FILE "esa-buffer" :DEPENDS-ON #) (:FILE "esa-io" :DEPENDS-ON #) (:FILE "esa-command-parser" :DEPENDS-ON #))))) #<NULL-LEXENV>) 6: (SB-FASL::LOAD-AS-SOURCE #<SB-SYS:FD-STREAM for "file /little/home/empty/desr/git/mcclim/mcclim.asd" {1002FABE21}> NIL NIL) 7: ((FLET SB-FASL::LOAD-STREAM) #<SB-SYS:FD-STREAM for "file /little/home/empty/desr/git/mcclim/mcclim.asd" {1002FABE21}> NIL) 8: (LOAD #P"/home/empty/desr/git/.asdf-registry/esa-mcclim.asd")[:EXTERNAL] 9: (FIND-SYSTEM :ESA-MCCLIM T) 10: ((SB-PCL::FAST-METHOD PERFORM :AROUND (T T)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<CLOSURE # {1002F99259}> :PV NIL :NEXT-METHOD-CALL NIL :ARG-INFO (2)) #<LOAD-OP NIL {1002F6F791}> #<CL-SOURCE-FILE "package" {1002EC6341}>) 11: ((SB-PCL::FAST-METHOD PERFORM AROUND (LOAD-OP CL-SOURCE-FILE)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV NIL :NEXT-METHOD-CALL #S(SB-PCL::FAST-METHOD-CALL :FUNCTION # :PV NIL :NEXT-METHOD-CALL NIL :ARG-INFO (2)) :ARG-INFO (2)) #<LOAD-OP NIL {1002F6F791}> #<CL-SOURCE-FILE "package" {1002EC6341}>) 12: ((LAMBDA ())) 13: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK)) 14: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]291)) 15: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {7FFFF519F9D9}> #S(SB-THREAD:MUTEX :NAME "World Lock" :%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {10029D7091}> :STATE 1)) 16: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA #) {1002F97EB9}>)[:EXTERNAL] 17: (OPERATE LOAD-OP :SB-ROTATE-BYTE)[:EXTERNAL] 18: (ASDF::MODULE-PROVIDE-ASDF :SB-ROTATE-BYTE) 19: ((LAMBDA (#:G[REQUIRE]13)) ASDF::MODULE-PROVIDE-ASDF) 20: (SB-IMPL::%MAP-FOR-EFFECT-ARITY-1 #<CLOSURE (LAMBDA #) {10053D3949}> (ASDF::MODULE-PROVIDE-ASDF SB-IMPL::MODULE-PROVIDE-CONTRIB)) 21: (REQUIRE :SB-ROTATE-BYTE NIL) 22: ((LAMBDA ())) 23: (SB-INT:SIMPLE-EVAL-IN-LEXENV (HANDLER-CASE (PROGN (REQUIRE :SB-ROTATE-BYTE) (PUSHNEW :SBCL-USES-SB-ROTATE-BYTE *FEATURES*)) (ERROR NIL (DELETE :SBCL-USES-SB-ROTATE-BYTE *FEATURES*))) #<NULL-LEXENV>) 24: (SB-INT:SIMPLE-EVAL-IN-LEXENV (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL :EXECUTE) (HANDLER-CASE (PROGN (REQUIRE :SB-ROTATE-BYTE) (PUSHNEW :SBCL-USES-SB-ROTATE-BYTE *FEATURES*)) (ERROR NIL (DELETE :SBCL-USES-SB-ROTATE-BYTE *FEATURES*)))) #<NULL-LEXENV>) 25: (SB-FASL::LOAD-AS-SOURCE #<SB-SYS:FD-STREAM for "file /little/home/empty/desr/git/cl-utilities/cl-utilities.asd" {10050BA141}> NIL NIL) 26: ((FLET SB-FASL::LOAD-STREAM) #<SB-SYS:FD-STREAM for "file /little/home/empty/desr/git/cl-utilities/cl-utilities.asd" {10050BA141}> NIL) 27: (LOAD #P"/home/empty/desr/git/.asdf-registry/cl-utilities.asd")[:EXTERNAL] 28: (FIND-SYSTEM "cl-utilities" T) 29: ((FLET #:FORM-FUN-[EXIT-TAG-[ASDF-HIDDEN-SYSTEM-NAMES]518]529)) 30: (DESIRE::ASDF-HIDDEN-SYSTEM-NAMES #S(CL-UTILITIES :MODULE DESIRE::CL-UTILITIES)) I find this effect too drastic for my liking. I hope I'm not alone on this :-) regards, Samium Gromoff -- _deepfire-at-feelingofgreen.ru O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

6 8

[asdf-devel] I'm too busy right now to be able to do a good job with ASDF
by Gary King 02 Dec '09

02 Dec '09

Hi, As you've all no doubt gathered, my time is hardly mine own these days and this looks to be a problem for at least the next six months. I've been living under the illusion that some personal stuff would be getting simpler sooner but I'm realizing that that is _not_ going to happen. sigh. So it's with regret that I need to say that I'm hardly the one to be doing ASDF maintenance and development right now. I'm happy to share the commit bit with those that would like it and hope to keep my hand in occasionally. I won't, however, be able to do anything at all far reaching. Enjoy! -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

4 5

[asdf-devel] Dangling link patch for asdf.texinfo
by Robert P. Goldman 01 Dec '09

01 Dec '09

Nuntius pointed out that this pointer to Kent Pitman's paper was broken. Patch plugs in the right one.

1 1

[asdf-devel] Resend of ASDF documentation patch
by Robert P. Goldman 01 Dec '09

01 Dec '09

This patch adds the method-form to the grammar table for defsystem.

1 1

[asdf-devel] Please test: merged ECL support, created asdf.asd
by Faré 01 Dec '09

01 Dec '09

Dear ASDF developers, I've committed to *a new repo* a few ASDF hacks that I wrote. I'd like some of you to review and/or test it. I'd like to get it reviewed before I push those changes to the official repo. git clone http://common-lisp.net/project/xcvb/git/asdf.git cd asdf git diff -u -a -b 1f7690b49b73b499ff2bd2ad77ec23c273941814 60165185516e699d0daebd0b653e61b83e72d4e6 The main changes are: * Merged the ECL patch. Had to remove a #+ecl in a slot declaration, because the slot is used afterwards without #+ecl. * Limited support to upgrade from a previous installation (if you have old installations, please try to upgrade!). * Notably created an asdf.asd so you can try to (require :asdf) (pushnew "/path/to/asdf/" asdf:*central-registry*) (asdf:oos 'asdf:load-op :asdf) * Some whitespace normalization (hence use -b in diff above). There are more things to do before we can declare asdf fully upgradable, but that's a first step. When all is done, there will be less pressure to synchronize with CL implementers to upgrade before a new feature can be relied upon. See https://bugs.launchpad.net/asdf/+bug/485687 Known issues (juanjo, help appreciated): $ ecl -eval "(require :asdf)" -load "asdf.lisp" ==> works $ ecl -eval "(require :asdf)" -eval "(asdf:oos 'asdf:load-op :asdf)" ==> fails ;;; Finished compiling /home/fare/cl/asdf/asdf.lisp. An error occurred during initialization: NIL is not of type HASH-TABLE.. Fails with both ECL 9.10.2 from debian and ECL 9.11.1 from a semi-recent clbuild. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] To make an apple pie from scratch, you must first create the universe. -- Carl Sagan

3 6

Re: [asdf-devel] Bizarre consequences of FIND-SYSTEM in ASDF.
by Robert Goldman 30 Nov '09

30 Nov '09

dherring(a)tentpost.com wrote: > Robert Goldman wrote: >> Daniel Herring wrote: >>> On Sun, 29 Nov 2009, Robert Goldman wrote: .... > > There would be several benefits if FIND-SYSTEM were to simply PROBE-FILE > for a system definition in each of the configured paths (e.g. > path1/system.asd, path2/system.asd) until one is found. Better > efficiency, no pollution from unrelated packages, etc. I still don't get it. I'm looking at asdf.lisp, and it's basically doing what you say: 1. call system-definition-pathname to find the system definition file. 2. if there's a previously-loaded system definition, check to see if it's stale. If so, reload. 3. If there's no previously-loaded system definition, load 4. return the system definition. In stock (upstream) asdf, there's no loading in sysdef-central-registry-search, so I still don't see what's going wrong here. Is this SBCL-specific? As for the fact that people can put code like (asdf:oos 'asdf:load-op <system I need at read time>) in their .asd files, that seems to me to be a feature, not a bug. r

1 0

[asdf-devel] Output Stream for ASDF
by thomas.bartscher＠widder-software.com 30 Nov '09

30 Nov '09

Why are warnings of asdf put into *standard-output*? Wouldn't it be easier to put those into something like *asdf-warnigs*? This way users of asdf could redirect those wherever they want.

3 2

[asdf-devel] duplicate-names for module and file with same name?
by Jianshi Huang 27 Nov '09

27 Nov '09

Hi, Currently in parse-component-form function, duplication of names are checked but modules and files are put to the same category. Is there any particular reason for this restriction? e.g. I can't have both foo.lisp foo/ in the same folder since (:module :foo) and (:file "foo") will conflict in names. Cheers, Jianshi Huang

2 2

[asdf-devel] ASDF::COERCE-NAME string-downcases symbols, but lets strings untouched
by Tobias C. Rittweiler 21 Nov '09

21 Nov '09

(defun coerce-name (name) (typecase name (component (component-name name)) (symbol (string-downcase (symbol-name name))) (string name) (t (sysdef-error "~@<invalid component designator ~A~@:>" name)))) I first thought this was some bad kludge to support modern-mode. But vc-annotate told me that was introduced by Nikodemus. What is the reason that symbols are downcased but strings not? It makes (FIND-SYSTEM :FOO) be different from (FIND-SYMBOL (SYMBOL-NAME :FOO)) which is just weird. -T.

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel