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

[asdf-devel] revising asdf manual
by Robert Goldman 12 Mar '10

12 Mar '10

The section 8/9 merge was easy. The section 7 (where does asdf write its files?) one is going to be more difficult. It turns out that this stuff is discussed in THREE locations: 1. The "configuring ASDF chapter; 2. Section 7 3. README.asdf-output-translations. Getting those three merged sensibly is going to be a bit more work than I'd hoped. I'm inclined to start by having the configuration chapter just crossref to section 7, and merge all the stuff into section 7. Then we can figure out how to reorganize things. I think we should probably update this to restore some one-paragraph "here's how you turn it on with a minimum of fuss" introduction. Regrettably, I don't see how that's possible with the full, heavyweight new configuration procedure. Cheers, r

2 1

[asdf-devel] texinfo documentation
by Faré 11 Mar '10

11 Mar '10

>> I can't find my way through the texinfo documentation. Too much manual >> section management. Could we be using something nicer? ReST? Exscribe? >> Gary King's CL-Markdown? > > Texinfo is standard and the toolchain is available to everyone. > > CL-Markdown has a big dependency chain, and a brittle one. > > If you use emacs, it will take care of all of the manual section > management: Texinfo > Update every node, Texinfo > Node..., Texinfo > > Create menu.... Similarly, emacs will take care of building for you, to > a number of different formats. > > So far, I'm pretty much the only one editing the manual. I promise to > stop if the format changes. > I understand. If you do the section work or walk me through it on IRC, I can do the filling the blanks for specifying how ASDF computes pathnames from module names, and what is or isn't portable to use. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The revolution will be won, not, as the authoritarians would claim, when the last political boss is hanged with the bowels of the last state propagandist, but, as the libertarians know, when the ever-repeated attempts to lure people into subservience are systematically greeted with laughter and drowned in ridicule by free men who are well-armed both physically and intellectually.

2 2

[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

[asdf-devel] web page wrong
by Robert Goldman 11 Mar '10

11 Mar '10

Still has Gary King's name and email on it. cheers, r

1 0

[asdf-devel] asdf:around method
by Faré 10 Mar '10

10 Mar '10

>> Oh my, the asdf:around fiasco again. ABCL apparently uses an old >> version of ASDF to avoid a lot DEFINE-METHOD-COMBINATION. >> >> Couldn't we instead just have a do-perform function do the wrapping >> stuff and call perform gf, and skip that method-combination >> complication? >> >> Is there a good reason to use this method-combination protocol? Does >> anyone rely on either defining asdf:around methods or on calling >> perform directly and having it do the restart magic? > > A lot of people use the Stale Fasl recipe at > > http://www.cliki.net/asdf > > which was the reason that prompted introducing the custom > method combination. > I certainly want to support this kind of recipe. I believe wrapping the one call to perform in a do-perform generic function that handles the restarts the way the asdf:around method currently does will provide this functionality. > Long form of D-M-C is in the works for ABCL from what I know. > Well, I suppose we can wait a bit. If by the time we're done documenting 2.0 they still have no deadline for D-M-C, we can think about removing it. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] No woman ever falls in love with a man unless she has a better opinion of him than he deserves. — Edgar Watson Howe

2 1

[asdf-devel] clx-0-7-4 fails to compile if the system pathname is logical
by james anderson 05 Mar '10

05 Mar '10

if the system pathname is logical, the component for the file "shape.lisp" fails to locate the intended file. * (asdf:operate 'asdf:load-op :de.setf.graphics.clx) ... ; loading system definition from ; /Development/Source/dev/Library/de/setf/graphics/clx/clx.asd into ... ;; loading #P"/Users/janson/.cache/common-lisp/sbcl-1.0.35-darwin- ppc32/Development/Source/dev/Library/bin/sbcl-osx/edu/mit/clx/ clx-0-7-4/resource.fasl" debugger invoked on a SB-INT:SIMPLE-FILE-ERROR: failed to find the TRUENAME of /edu/mit/clx/clx-0-7-4/shape.lisp: No such file or directory the problem occurs because the respective module, "extensions", specifies a relative pathname with the directory component (:relative) but no host. the consequence is that the source file's relative pathname is an absolute pathname relative to "/" rather than relative to the logical base. the system: 8] (describe *s*) #<ASDF:SYSTEM "clx" {11D57A31}> [standard-object] Slots with :INSTANCE allocation: NAME = "clx" VERSION = "0.7.2" IN-ORDER-TO = ((ASDF:LOAD-OP (ASDF:LOAD-OP CLX- SYSTEM::SB-BSD-SOCKETS)).. DO-FIRST = ((ASDF:COMPILE-OP (ASDF:LOAD-OP CLX- SYSTEM::SB-BSD-SOCKETS))) INLINE-METHODS = NIL PARENT = NIL RELATIVE-PATHNAME = #P"LIBRARY:EDU;MIT;CLX;CLX-0-7-4;" OPERATION-TIMES = #<HASH-TABLE :TEST EQL :COUNT 0 {11E8C2F1}> PROPERTIES = ((ASDF:SYSTEM-NICKNAMES "edu.mit.clx.clx")) COMPONENTS = (#<CLX-SYSTEM::CLX-SOURCE-FILE "package" {120E8811}>.. IF-COMPONENT-DEP-FAILS = :FAIL DEFAULT-COMPONENT-CLASS = CLX-SYSTEM::CLX-SOURCE-FILE DESCRIPTION = #<unbound slot> LONG-DESCRIPTION = #<unbound slot> AUTHOR = #<unbound slot> MAINTAINER = #<unbound slot> LICENCE = #<unbound slot> SOURCE-FILE = #P"/Development/Source/dev/Library/edu/ mit/clx/clx-0-7-4/clx.asd" the module: 8] (describe *p*) #<ASDF:MODULE "extensions" {11E29EA9}> [standard-object] Slots with :INSTANCE allocation: NAME = "extensions" VERSION = #<unbound slot> IN-ORDER-TO = ((ASDF:LOAD-OP.. DO-FIRST = ((ASDF:COMPILE-OP.. INLINE-METHODS = NIL PARENT = #<ASDF:SYSTEM "clx" {11D57A31}> RELATIVE-PATHNAME = #P"" OPERATION-TIMES = #<HASH-TABLE :TEST EQL :COUNT 0 {120E8AE1}> PROPERTIES = NIL COMPONENTS = (#<CLX-SYSTEM::CLX-SOURCE-FILE "shape" {123FA861}>.. IF-COMPONENT-DEP-FAILS = :FAIL DEFAULT-COMPONENT-CLASS = CLX-SYSTEM::CLX-SOURCE-FILE 8] (describe (asdf:component-relative-pathname *p*)) #P"" [structure-object] Slots with :INSTANCE allocation: HOST = #<SB-IMPL::UNIX-HOST {102CE661}> DEVICE = NIL DIRECTORY = (:RELATIVE) NAME = NIL TYPE = NIL VERSION = NIL the file component 8] (describe *c*) #<CLX-SYSTEM::CLX-SOURCE-FILE "shape" {123FA861}> [standard-object] Slots with :INSTANCE allocation: NAME = "shape" VERSION = #<unbound slot> IN-ORDER-TO = NIL DO-FIRST = ((ASDF:COMPILE-OP (ASDF:LOAD-OP))) INLINE-METHODS = NIL PARENT = #<ASDF:MODULE "extensions" {11E29EA9}> RELATIVE-PATHNAME = NIL OPERATION-TIMES = #<HASH-TABLE :TEST EQL :COUNT 0 {126394B9}> PROPERTIES = NIL 8] (describe (asdf:component-pathname *c*)) #P"/edu/mit/clx/clx-0-7-4/shape.lisp" [structure-object] Slots with :INSTANCE allocation: HOST = #<SB-IMPL::UNIX-HOST {102CE661}> DEVICE = :UNSPECIFIC DIRECTORY = (:ABSOLUTE "edu" "mit" "clx" "clx-0-7-4") NAME = "shape" TYPE = "lisp" VERSION = :NEWEST the excerpt from the system definition: (:module extensions :pathname #.(make-pathname :directory '(:relative)) :components ((:file "shape") (:file "big-requests") (:file "xvidmode") (:xrender-source-file "xrender") (:file "glx") (:file "gl" :depends-on ("glx")) (:file "dpms") (:file "xtest") (:file "screensaver") (:file "xinerama")))

1 0