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

[asdf-devel] ASDF works again with ECL (also a question)
by Juan Jose Garcia-Ripoll 23 Mar '10

23 Mar '10

Thansk for the latest changes, they work like a charm now. I have done something which I do not know whether it is a desired protocol. Namely I have submitted patches for asdf-ecl.lisp using launchpad. I did this because I always found it more convenient to have a look at the ECL bug/patch tracker thank keeping track of the emails with patches and remember whether they were committed. Is it ok? Should I continue doing so with the following patches, such as test cases, etc? Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

2 4

[asdf-devel] Minor comments regarding manual on HEAD
by Tobias C. Rittweiler 21 Mar '10

21 Mar '10

* README should say how to build the manual * That said, how is the user supposed to build the manual? There does not seem to be any rule for it in the Makefile. * texipdf asdf.texinfo resulted in an error; an asdf.pdf was produced nontheless. See PS for transcript. * the manual should perhaps start with a "What's new" section which mostly contains links to the appropriate pages. -T. PS. tcr@thaleron:~/src/from-upstream/asdf$ texi2pdf asdf.texinfo This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) file:line:error style messages enabled. %&-line parsing enabled. entering extended mode (./asdf.texinfo (/usr/share/texmf/tex/texinfo/texinfo.tex Loading texinfo [version 2008-04-18.10]: pdf, fonts, page headings, tables, conditionals, indexing, sectioning, toc, environments, defuns, macros, cross references, insertions, (/usr/share/texmf-texlive/tex/generic/epsf/epsf.tex This is `epsf.tex' v2.7.3 <23 July 2005> ) localization, formatting, and turning on texinfo input format.) (./asdf.aux) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2] (./asdf.toc) [-1] (./asdf.toc) (./asdf.toc) Chapter 1 l.149: Undefined cross reference `The object model of ASDF-pg'. Chapter 2 [1] [2] l.288: Undefined cross reference `Getting the latest version-snt'. l.288: Undefined cross reference `Getting the latest version-snt'. l.288: Undefined cross reference `Getting the latest version-pg'. Chapter 3 [3] l.309: Undefined cross reference `Controlling where ASDF searches for systems-s nt'. l.309: Undefined cross reference `Controlling where ASDF searches for systems-s nt'. l.309: Undefined cross reference `Controlling where ASDF searches for systems-p g'. Underfull \hbox (badness 3271) in paragraph at lines 311--318 []@textrm The de-fault lo-ca-tion for a user to in-stall Com-mon Lisp soft-ware is un-der [4] l.458: Undefined cross reference `Controlling where ASDF saves compiled files-s nt'. l.458: Undefined cross reference `Controlling where ASDF saves compiled files-s nt'. l.458: Undefined cross reference `Controlling where ASDF saves compiled files-p g'. Underfull \hbox (badness 6641) in paragraph at lines 460--468 []@textrm The sim-plest way to add a trans-la-tion to your search path, say fro m Underfull \hbox (badness 4846) in paragraph at lines 460--468 @textrm `@texttt /foo/bar/baz/quux/[]@textrm '[] to `@texttt /where/i/want/my/f asls/[]@textrm '[] is to cre-ate the di-rec-tory [5] Underfull \hbox (badness 3492) in paragraph at lines 484--490 []@textrm Note that your Op-er-at-ing Sys-tem dis-tri-bu-tion or your sys-tem a d-min-is-tra-tor Underfull \hbox (badness 2229) in paragraph at lines 484--490 @textrm may al-ready have con-fig-ured trans-la-tions for you. In ab-sence of a ny con-fig-u- Underfull \hbox (badness 2662) in paragraph at lines 484--490 @textrm ra-tion, the de-fault is to redi-rect ev-ery-thing un-der an implementa tion-dependent Underfull \hbox (badness 10000) in paragraph at lines 484--490 @textrm sub-di-rec-tory of `@texttt ~/.cache/common-lisp/[]@textrm '[]. Once ag ain, see the doc-u-ment Chapter 4 [6] Chapter 5 [7] [8] Overfull \hbox (32.02371pt too wide) in paragraph at lines 766--766 [][] | [9] [10] Underfull \hbox (badness 2951) in paragraph at lines 843--847 []@textrm To use log-i-cal path-names, you will have to pro-vide a path-name ob -ject as a [11] Chapter 6 [12] ./asdf.texinfo:1006: Argument of & has an extra }. <inserted text> @par <to be read again> } @tclose ...n @rawbackslash @plainfrenchspacing #1} @null @codex #1->@tclose {#1} @endgroup <argument> ...eration} @var {system} @code {&rest} @var {initargs} @unskip @defunargs ...ar @font =0 @let @var =@ttslanted #1 @sl @hyphenchar @font =45 ... l.1006 ...@var{system} @code{&rest} @var{initargs} ?

4 6

[asdf-devel] ASDF and source file extensions
by Juan Jose Garcia-Ripoll 19 Mar '10

19 Mar '10

In a system such as (defsystem :foo :component ((:file "foo"))) where foo.lsp exists and is recognized by the lisp implementation as a valid source file (ECL), ASDF imposes the file extension "lisp". Furthermore, adding our own extension (defsystem :foo :component ((:file "foo.lsp"))) does not work and one has to resort to an EQL-specialized method (ugly!) I have submitted a small patch that adds a new option :type that can be used with components of the type source-file https://bugs.launchpad.net/asdf/+bug/542222 -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

1 0

[asdf-devel] quick launchpad question
by Robert Goldman 19 Mar '10

19 Mar '10

would it be possible to also add a "version 3" milestone so that we could explicitly push stuff /out/ of version 2? Right now it seems like there's no way of telling the difference between "unmilestoned" and "milestoned out of version 2". But my ignorance of launchpad is near complete, so it is possible I am missing something. thanks, r

2 1

[asdf-devel] Preparation for ASDF 2: launchpad
by Robert Goldman 19 Mar '10

19 Mar '10

Would it be possible for someone to add an "ASDF 2 release" (or something equivalent) milestone to launchpad? As we get close to this point, it would be nice to triage the launchpad tickets either into our out of ASDF 2. thanks, r

1 0

[asdf-devel] ASDF traverse changed behavior?
by Juan Jose Garcia-Ripoll 19 Mar '10

19 Mar '10

Before, if an operation defined by me, such as LIB-OP, did not traverse a system, then the only operation we got was that operation applied on the system, as a generic object. Now TRAVERSE not only imposes the LIB-OP operation on the system, but it also scans the components and imposes the operation on the components. Why such an incompatible change? It definitely screwed up ALL of ECL's extensions. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

4 34

[asdf-devel] hooking into cl:require on ccl
by R. Matthew Emerson 18 Mar '10

18 Mar '10

Some users apparently like cl:require to use ASDF to provide modules. In http://trac.clozure.com/ccl/changeset/12260, we added code to ccl that will do this if ASDF is loaded. It seems to me that this really belongs in upstream ASDF. The already-present-in-ASDF SBCL-specific code to do this looks like it could be adapted to work on ccl also. If the answer is "we would welcome a patch", I can try to provide one, but I barely know how to work ASDF, and I'm hoping that some generous ASDF committer will be able to make the changes. Then, when ASDF2 is ready, I can import it into ccl, and remove r12260.

2 1

Re: [asdf-devel] New issue testing with ACL: oddity with output translations
by Robert Goldman 18 Mar '10

18 Mar '10

On 3/17/10 Mar 17 -9:15 PM, Faré wrote: > Fixed. I hope. Oops. Super, thanks. And I picked off a couple of buglets in the tests, so they are looking better than ever. Only one (explained) failure on ACL! > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] > A language that doesn't affect the way you think about programming, > is not worth knowing. — Alan Perlis A lisp programmer knows the value of everything and the cost of nothing. ;-)

1 0

[asdf-devel] New issue testing with ACL: oddity with output translations
by Robert Goldman 18 Mar '10

18 Mar '10

I just tried to run the tests on ACL and got a new failure. Please pay particular attention to the lines preceded with **, which indicate to me that something's going wrong with the output translations, with "alisp" somehow turning into "case-insensitive-upperlisp". I will try to figure out if I can find out what's doing this, but I could use any clues that anyone could offer... [rpgoldman-2:~/lisp/asdf/test] rpg% ./run-tests.sh -d allegro alisp is /usr/local/acl/acl81/alisp PRIVATE_ASDF_INSTALL_DIR=/Users/rpg/lisp/asdf-install-systems CL_SOURCE_REGISTRY=/Users/rpg/lisp/asdf ** ASDF_OUTPUT_TRANSLATIONS=/Users/rpg/lisp/asdf:/Users/rpg/lisp/asdf/tmp/fasls/alisp: PWD=/Users/rpg/lisp/asdf/test + alisp -q -e '(load "test/compile-asdf.lisp")' ;;; Installing locale patch, version 1. ; Loading /Users/rpg/lisp/asdf/test/compile-asdf.lisp ; Loading /Users/rpg/lisp/asdf/test/script-support.lisp ;;; Compiling file /Users/rpg/lisp/asdf/asdf.lisp ; Autoloading for package "ASDF": ; Fast loading /usr/local/acl/acl81/code/ASDF.fasl ; Autoloading for package "EXCL.OSI": ; Fast loading /usr/local/acl/acl81/code/OSI.004 ;;; Installing osi patch, version 4. ; Fast loading from bundle code/fileutil.fasl. ; Autoloading for package "REGEXP": ; Fast loading from bundle code/regexp2-s.fasl. ;;; Installing regexp2-s patch, version 1. ; Autoloading for REGEXP::MAKE-VM-CLOSURE: ; Fast loading /usr/local/acl/acl81/code/regexp2.fasl ; Fast loading /usr/local/acl/acl81/code/YACC.fasl Function (FLET SYSTEM-CONFIGURATION-DIRECTORIES TRY) is never used. ;;; Writing fasl file ** ;;; /Users/rpg/lisp/asdf/tmp/fasls/case-insensitive-upperlisp/asdf-tmp.fasl ;;; Fasl write complete Testsuite failed: ASDF compiled with warnings ; Exiting Compilation FAILED

1 0

[asdf-devel] ECL testing issue
by Faré 17 Mar '10

17 Mar '10

http://ec2-174-129-63-37.compute-1.amazonaws.com/test/log/20100316T233422/e… On 17 March 2010 10:01, james anderson <james.anderson(a)setf.de> wrote: > what might the error in the cited transcript indicate as the cause > for the problem with ecl? here is one entry: > > Testing: asdf-pathname-test.script > ;;; Loading "/ebs/test/asdf/test/asdf-pathname-test.script" > ;;; Loading #P"/ebs/test/asdf/test/script-support.lisp" > ;;; Loading #P"/development/lib/ecl-10.2.1/cmp.fas" > ;;; Loading #P"/development/lib/ecl-10.2.1/sysfun.lsp" > ;;; Loading "/ebs/test/asdf/tmp/asdf-ecl.fas" > An error occurred during initialization: > LOAD: Could not load file #P"/ebs/test/asdf/tmp/asdf-ecl.fas" (Error: > "/ebs/test/asdf/tmp/asdf-ecl.fas: invalid ELF header"). > Using ecl , asdf-pathname-test.script failed > I think one ominous thing in the transcript is: Reusing previously-compiled ASDF Try cleaning your tmp/ directory and see if it works any better. [ 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 2