asdf-devel January 2010

asdf-devel@common-lisp.net

15 participants
23 discussions

[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] 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] ASDF 1.501
by Faré 02 Feb '10

02 Feb '10

I've just released ASDF 1.501 in the official repository, now with all the source registry configuration that I previously discussed. It's currently documented in its own file README.source-registry, rather than in the general manual asdf.texinfo, as it should be. Patch welcome. Note that I bumped the version from 1.375 to 1.500 then 1.501. This to indicate that we're not using CVS anymore, that I've reached a milestone towards my goal of an "ASDF 2" that I could push as a replacement to ASDF. It passes the tests with SBCL. But the tests could be extended to do more. 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? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] "If men are good, you don't need government; if men are evil or ambivalent, you don't dare have one." — Robert LeFevre

5 17

[asdf-devel] asdf output locations
by Faré 02 Feb '10

02 Feb '10

My plan for ASDF 1.600 is to rename the (recently) builtin asdf-binary-locations to asdf-output-locations and make a few incompatible changes to it. * These changes will allow for configuration through an API similar to the one I introduced for the source-registry in 1.500. * I don't think many people use bleeding-edge enough ASDF to have the builtin ABL and these kinds of people would easily adapt anyway * This API will allow the future common-lisp-controller to plug nicely into ASDF through a supported API that doesn't break other stuff and isn't broken by it. * It will also bring all the binary location advantages of asdf-binary-locations, common-lisp-controller or CL-launch to everyone with a single, well-documented, supported configuration mechanism. I committed the following document to explain my current plans, and would appreciate comments: http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git;a=blob;f=README.asdf… [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Wishing without work is like fishing without bait. — Frank Tyger

5 13

[asdf-devel] Question about git
by Robert Goldman 31 Jan '10

31 Jan '10

How are we supposed to be reasoning about the multiple git repositories out there? I have been pulling from the master/public one and then working locally. Fare works on his personal working copy. When I make a patch on mine, based on public, seems like I sometimes end up with patches that Fare can't apply cleanly to his. How are we supposed to handle this? Thanks, r

5 12

Re: [asdf-devel] asdf v 1.501: doesn't look at /etc/common-lisp/source-registry.conf.d/
by Faré 30 Jan '10

30 Jan '10

Oops, you're right. So here's ASDF 1.502. Also includes a fix to bug 513338 (ccl support in test). [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Living your life is a task so difficult, it has never been attempted before. On 30 January 2010 16:14, Peter Van Eynde <pvaneynd(a)debian.org> wrote: > Looking into the code I vaguely think that we are missing a call to > > (process-source-registry (system-source-registry-directory-pathname) > > somewhere, not?

1 0

Re: [asdf-devel] Bug#560781: (require :package) no longer works for CLC-managed packages
by Faré 29 Jan '10

29 Jan '10

2010/1/20 Peter Van Eynde <pvaneynd(a)mailworks.org>: > instead of /etc/common-lisp/source-registry.conf I would like to see > /etc/common-lisp/source-registry.conf.d > > where instead of having one file that you might have to edit in > post-installation scripts we would have a directory where packages can > just drop files into. Just like we have /etc/crontab and /etc/cron.d/* > on Debian. > > This would make my and I suspect others work much easier. > Makes perfect sense. I'll add that on top of my TODO list for ASDF. Would that replace source-registry.conf altogether, or override it, or be overridden by it? >> Since ASDF-BINARY-LOCATIONS is now part of ASDF, I suppose it could be >> similarly configured, and CLC could and should "just" use that. What >> do you think? > > I just noticed this in the manual and need to read it with more > attention later. Ideally I would like it to handle also 'cached' fasl > files from a trusted system user. Would it be able to do this too? > I probably would do it, if we coax it to our will. Definitely possible. I admit I never looked into ABL myself, having only ever used but my own variant (included in cl-launch) that itself is derived from an earlier CLC and works well with CLC. Hopefully, moving ABL into ASDF was a good move, and we should get the configuration of it right. > So load from > /var/cache/common-lisp-controller/cl-builder/<implementation>/... > or > /var/cache/common-lisp-controller/<userid>/<implementation>/... > or compile from /usr/share/common-lisp-controller/source/... to > /var/cache/common-lisp-controller/<userid>/<implementation>/... > Yes. All the while, the default might be something like ~/.cache/common-lisp/<same-tag-as-slime>/... > Related: I might go for a business trip to Boston in the near future and > would love to have a chat! I would love to see you again! [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] He who refuses to do arithmetic is doomed to talk nonsense. — John McCarthy, in his webpage on Progress and Sustainability

2 2

[asdf-devel] subtle bugfix [for clisp on windows]
by dherring＠tentpost.com 28 Jan '10

28 Jan '10

Thank you git-bisect. The attached patch fixes my problems with asdf and clisp on mswinxp32. It fixes what I believe was a typo in commit 2ca055895. Surprisingly, it works on most implementations. - Daniel

2 1

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

27 Jan '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/ iQIcBAEBCAAGBQJLX9WFAAoJEB4VNT76eIlapncQAI+DYsBLpm9Xh11vNKuSrFJV ZitxL7/MF/u16nC6JAeN/U5mPgd8ZR4osEsupvYWKzmQvmZDvPYZ4LXV9nIWKptq +oKSb7/Gv9ft3KU6r5kgtp62/3Qf8e7oyf4NBnfZFlW+OSpWxywca5gtl7U9KvWd F34s4kK8zRvHTAbKCp06LdkDo9C4UhQwlk21M7q3ZOTuPc3JhEp5oVZXqUfi2qUb q+gx01jL0ArFR/vjuVxwbWmVgldgKzAkdIl3IVcn+PsuJBheTLzqQl2YATNRNYO0 NfMbmNEYgWm4acip+jj3juehoYELL8zCxADFQIo3KDi1fZxZ286x5B4ca0OWM9GX KV3RZIl66zq+oeZZOykI37xPlreCOD8rIdNFMqxCavu82GGRYWjtPdm1w8HGBr8O zGohjN7QZhCI3jJNO20i+ubZ8Bq1AU6TM9MAYT/6byzwOHQKQ5nXcYUqEaB6XEs+ GKXhHS6ee182LUK7AfaVV+WYgsiuubEX8mQm0X/wc+xJquTsoUMA6wxdezMWkUGs RsOuaBR2VSnVTF7RNJQXBJDb39If3jeT5QJfTfhyv9x2jTpx3ssONcfSYibU3ZKU 3N6LNevXjyQlJO/X87rVicDSCSCfX+gibxI+ZMdbksGrPJdCka1vGqKKKwbABOYr XNrBgxc85+sH/Ih7MCPg =Ul83 -----END PGP SIGNATURE-----

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel January 2010