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

[asdf-devel] Fwd: ASDF testing for LWW
by Dave Cooper 08 Apr '15

08 Apr '15

FYI It looks like some more command line escaping tweaks are needed for LWW. I'm on an outing today and will be able to run tests tonight with the latest commit. ---------- Forwarded message ---------- From: *Fabrice Popineau* Date: Sunday, October 20, 2013 Subject: ASDF testing for LWW To: Dave Cooper <david.cooper(a)genworks.com> The test suite fails by me with LWW : here at ligne 91 of run-tests.sh if DO $bcmd $eval "'(#.(load(string'|script-support.lisp|))#.(asdf-test::load-asdf)#.(asdf-test::frob-packages)#.(asdf-test::with-test()(load(string'|$i|))))" ; then $ ./run1 make[1]: Entering directory `/c/temp/asdf-test/asdf-windows' PWD=/c/temp/asdf-test/asdf-windows/test !C:=C:\Temp\asdf-test ASDF_TEST_LISPS=lispworks OLDPWD=/c/temp/asdf-test/asdf-windows /c/Local/Lispworks/lw-console.exe -siteinit - -init - -eval "(or #.(load(string\ `|test/script-support.lisp|))#.(asdf-test::compile-asdf-script))" LispWorks(R) (for the Windows(R) operating system) Copyright (C) 1987-2012 LispWorks Ltd. All rights reserved. Version 6.1.1 Saved by Fabrice as lw-console, at 20 Oct 2013 11:59 User Fabrice on ALIMANTADO Error: The file "testscript-support.lisp" does not exist. 1 (continue) Try loading testscript-support.lisp again. 2 Give up loading testscript-support.lisp. 3 Try loading another file instead of testscript-support.lisp. 4 (abort) Abort initialization. 5 Continue to top-level loop. I'm not that familiar with path syntax in CL (I'm using it at its minimum and always checking) so why is there this (string`|path|) ? Case-sensitivity ? Or ? Fabrice 2013/10/20 Dave Cooper <david.cooper(a)genworks.com <javascript:_e({}, 'cvml', 'david.cooper(a)genworks.com');>> > > > Have you been waiting for the noise to settle down on asdf-devel? I think > it's safe to go ahead and try the tests on LWW now. > > I've attached a "run" script which should be pretty much ready to go for > LWW, all you have to do is fill in your lwconsole.exe location where it > says: > > "Fill in for location of your LWW console exe:" > > You have to have "make" and "rsync" installed in your MSYS (or cygwin) > (rsync is probably not strictly necessary; for running on a single OS you > can just replace $asdf with the original "asdf/" directory). > > I'll be away from the office tomorrow (Sunday) but if you feel like giving > it a go on Sunday and run into any issues, feel free to give me a call on > skype or +1 248-330-2979. > > > > On Thu, Oct 17, 2013 at 5:50 PM, Fabrice Popineau < > fabrice.popineau(a)supelec.fr <javascript:_e({}, 'cvml', > 'fabrice.popineau(a)supelec.fr');>> wrote: > >> Ok, I'll reply about it on Saturday. >> >> Best regards, >> >> Fabrice >> >> >> 2013/10/17 Dave Cooper <david.cooper(a)genworks.com <javascript:_e({}, >> 'cvml', 'david.cooper(a)genworks.com');>> >> >>> >>> Basic instructions to run the tests: >>>> >>>> 1. Establish a directory to be the root of your testing area. >>>> 2. cd to this directory. >>>> 3. git clone git://common-lisp.net/projects/asdf/asdf.git >>>> 4. put the attached script into this directory >>>> >>> >>> >>> To be clear, by "this directory" I mean the _current_ directory, not the >>> asdf/ subdirectory which was newly created by the git clone. So the "run" >>> script and your pwd should both be in the parent of the asdf/ subdirectory >>> created by the git clone. >>> >>> >>> >>>> 5. edit the script to point to your LWW console image >>>> 6. ./run >>>> 7. observe the output in ./asdf/build/results/lispworks.text >>>> 8. If interesting, report the output to asdf-devel(a)common-lisp.net<javascript:_e({}, 'cvml', 'asdf-devel(a)common-lisp.net');> >>>> >>> > > > > -- > My Best, > > Dave Cooper, Genworks Support > david.cooper(a)genworks.com <javascript:_e({}, 'cvml', > 'david.cooper(a)genworks.com');>, dave.genworks.com(skype) > > -- Fabrice Popineau ----------------------------- SUPELEC Département Informatique 3, rue Joliot Curie 91192 Gif/Yvette Cedex Tel direct : +33 (0) 169851950 Standard : +33 (0) 169851212 ------------------------------ -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

3 4

[asdf-devel] Re: Preview of my ASDF3 article.
by Faré 08 Apr '15

08 Apr '15

I refactored that paper by making separate "short" (8 pages) and "extended" versions (24 pages), thereby fitting the limit while being able to say everything I had on my heart. I submitted the short PDF to ELS 2014. I also moved the papers to a more permanent location. [Source] https://github.com/fare/asdf3-2013/blob/master/asdf3-2014.scrbl [Extended HTML] http://fare.tunes.org/files/asdf3/asdf3-2014.html [Extended PDF] http://fare.tunes.org/files/asdf3/asdf3-2014.pdf [Short HTML] http://fare.tunes.org/files/asdf3/asdf3-els2014.html [Short PDF] http://fare.tunes.org/files/asdf3/asdf3-els2014.pdf I still need to extend the section on pathnames some more, but the short version should be stable, and even the extended version. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The worst thing that can happen to a good cause is, not to be skillfully attacked, but to be ineptly defended. — F. Bastiat

2 1

[asdf-devel] errors in ASDF 3.1.0.66
by Anton Vodonosov 08 Apr '15

08 Apr '15

Hello. I've been testing ASDF 3.1.0.66 and unfortunately detected errors: 1. Required method PERFORM not implemented for operation #<STANDARD-CLASS CFFI-GROVEL::PROCESS-OP {599AF195}>, component #<STANDARD-CLASS ASDF/LISP-ACTION:CL-SOURCE-FILE {582A1E35}> 2. New ASDF breaks ECL for Quicklisp. The problem nails down to (require 'sockets). This form works for ECL unless new ASDF is loaded. To reproduce at cl-test-grid.cloud.efficito.com machine: rlwrap ~/lisps/ecl-bin-13.5.1/bin/ecl -norc (require 'sockets) ;;; Loading #P"/home/testgrid/lisps/ecl-bin-13.5.1/lib/ecl-13.5.1/sockets.fas" => ("SB-BSD-SOCKETS" "SOCKETS") ------ compare with: rlwrap ~/lisps/ecl-bin-13.5.1/bin/ecl -norc -load ~/asdf/build/asdf.lisp (require 'sockets) ASDF could not load sockets because In function MAPCAR, the value of the second argument is #P"SYS:SOCKETS.FAS" which is not of the expected type LIST. The report: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-33.html Best regards, - Anton

2 5

[asdf-devel] READTABLE isolation in ASDF
by Robert P. Goldman 08 Apr '15

08 Apr '15

Attila Lendvai wrote: > this reminds me of the general idea of backwards compatibility: people > who want to live without this feature can chose not to upgrade, as > always. or if they need the new stuff, then they can just patch asdf > locally to disable the enforcement of this. or asdf could even > accommodate this with a defsystem property that can opt a system out > of this otherwise useful isolation. Yes, that is right; please see my earlier email with next steps: 1. The READTABLE isolation feature WILL NOT BE IN THE NEW RELEASE. 2. When/if it is released, the READTABLE isolation feature will only be an *opt-in* strict mode item. Thanks! R

1 0

[asdf-devel] Pushed 3.1.0.50 -- non-release version
by Robert P. Goldman 08 Apr '15

08 Apr '15

Fixed minor warning issue that caused a test problem on ACL. Added a check for BUNDLE-OP on unsupported platforms (ABCL + Mac OSX; ECL + Mac OSX). Cheers, r

2 1

[asdf-devel] uiop/filesystem:directory-files
by Станислав Кондратьев 08 Apr '15

08 Apr '15

Hello, I tried uiop and discovered two issues. I had installed uiop using quicklisp. The first issue looks like a bug: if I list the files of my home directory in CLISP, every file is included in the list twice as if the directory were listed two times. This takes place no matter if I specify the directory as "~/" or spell it out, and also if I run CLISP in my home directory and use uiop/os:getcwd. However, the function works normally with directories other than the home one. I did not specify wildcards in either case. I have observed this behaviour on Debian and OpenSuse. The second issue looks like a discrepancy between implementations: while in CLISP uiop/filesystem:directory-files returns a list of files (not subdirectories), in SBCL the directories are included into the output. I wonder at least which behaviour is the intended one. Best regards, Stanislav.

3 3

[asdf-devel] component-load-dependencies
by Didier Verna 08 Apr '15

08 Apr '15

Hello, currently Declt advertises component dependencies by using COMPONENT-LOAD-DEPENDENCIES. This function however only returns a list of symbols naming the components. What would be the best way to retrieve a list of component objects instead ? Thanks! -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

2 6

[asdf-devel] ASDF 3.0.3 ported to MKCL 1.1.7
by Jean-Claude Beaudoin 08 Apr '15

08 Apr '15

Hello ASDF maintainers, I just completed a port of ASDF 3.0.3 to what will soon be released as MKCL 1.1.7. It currently passes all the 48 tests of yours on Linux (Ubuntu 12.04) and I will very soon test it on Win32 and Win64 (I expect a routine ride there). I would like to submit back to you the few lines of ASDF code I had to conditionalize to get this port working OK. Can we do this through a "Pull request" on github? I see both a fare/asdf and a rpgoldman/asdf repositories that look like the head of ASDF evolution which one should I fork, merge with and then send the pull? Cheers, JCB

3 5

Re: [asdf-devel] Advanced Configuration
by FAU 08 Apr '15

08 Apr '15

I corrected it to your advice accordingly. (defmethod output-files ((operation compile-op) (component foo-file)) (multiple-value-bind (pathnames translatep) (call-next-method) (values (mapcar #'(lambda (p) (make-pathname* :directory (append (pathname-directory p) (list (cond ((featurep :foo1.0) "1.0") ((featurep :foo1.1) "1.1") (t (error "No foo feature found."))))) :defaults p)) pathnames) translatep))) On Sat, 2013-11-16 at 17:34 -0500, Faré wrote: > On Sat, Nov 16, 2013 at 5:21 PM, FAU <fau(a)riseup.net> wrote: > > (defmethod output-files ((operation compile-op) (component foo-file)) > > (let ((l (multiple-value-list (call-next-method)))) > > (apply #'values (mapcar #'(lambda (p) > > (make-pathname* :directory (append (pathname-directory p) (list # > > +foo1.0 "1.0" #+foo1.1 "1.1")) :defaults p)) > > (car l)) > > (cdr l)))) > > > Inasmuch as I think that runtime conditionals should be used rather than > compile-time conditionals wherever performance permits (see also featurep), > your general scheme is valid. However, you can should be using > (multiple-value-bind (pathnames translatedp) ... > (values ...)) > There are only two values returned in this protocol. > > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org > When my contradictors' ideas aren't an incoherent mess I can easily disprove, > I call them for the ideologists they are; but they are so dogmatic, > they don't change their mind after I insult them. >

1 0

[asdf-devel] Ready to release?
by Faré 08 Apr '15

08 Apr '15

I tweaked the upgrade to punt more on abcl, and it looks like it's working. cmucl, on the other hand, is desperately borking on upgrade, with or without punt. Apart from that, asdf 3.0.2.28 passes all tests for me on linux, including upgrade tests (except on cmucl), for ccl clisp sbcl cmucl allegro allegromodern abcl I also ran tests (but not upgrade tests yet) successfully for: ecl ecl_bytecodes lispworks xcl A few minor patches ago, I also tested that it can be compiled and run correctly on genera. I admit I'm growing impatient for a release 3.0.3 of ASDF. —♯ƒ • 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 10