asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] About asdf:*compile-file-failure-behaviour* and its value on SBCL
by Chun Tian (binghe) 20 Mar '11

20 Mar '11

Hi, ASDF developers I think asdf:*compile-file-failure-behaviour* should never been set to :error, just :warn is good. CLHS [1] said about COMPILE-FILE's 2nd and 3rd return values: "The secondary value, warnings-p, is false if no conditions of type error or warning were detected by the compiler, and true otherwise. "The tertiary value, failure-p, is false if no conditions of type error or warning (other than style-warning) were detected by the compiler, and true otherwise." This means, any warnings other than style-warning will cause COMPILE-FILE return T on its third return value. Than every Lisp file which contains a general (WARN "...") form, when compiling, will cause COMPILE-FILE return T on its third return value, and therefore was marked as "failure" (by ASDF). In current asdf.lisp, asdf:*compile-file-failure-behaviour* was defined as follow: (defvar *compile-file-failure-behaviour* (or #+sbcl :error #+clisp :ignore :warn) "How should ASDF react if it encounters a failure (per the ANSI spec of COMPILE-FILE) when compiling a file? Valid values are :error, :warn, and :ignore. Note that ASDF ALWAYS raises an error if it fails to create an output file when compiling.") I don't know why SBCL here is special, but this definition caused my project (cl-net-snmp 6.0) failed to be compiled by ASDF "only" on SBCL. Just try to put following lines in your ASDF based project and try to build it: (eval-when (:compile-toplevel) (warn "xxx")) you'll find how ludicrous the current setting of asdf:*compile-file-failure-behaviour* are. Regards, Chun Tian (binghe) [1] http://www.lispworks.com/documentation/HyperSpec/Body/f_cmp_fi.htm#compile-…

4 7

[asdf-devel] 2.013 later this week
by Faré 18 Mar '11

18 Mar '11

Dear ASDF users, unless you have requests for urgent bugs and/or object to some of the changes I just made (see below), I intend to release 2.013 later this week. Changes since 2.012: * cleanup in use of features. Introducing #+asdf-unix and #+asdf-window. (2.012.1) * cleanup in support for clisp. Implementation identifier vs processor name (2.012.2) * support for Digitool's legacy system (R)MCL (2.012.3) - as requested by p-cos to test his library. * cleanup when using portable pathnames (2.012.4) * cleanup in support for ECL (2.012.5, 2.012.6) * parse the pathname of a defsystem portably when it's a string. (2.012.7) * support for Symbolics' legacy system Genera (2.012.8) - proof of concept, completes legacy support and allowed me to test my libraries. * support for .. as :back in our portable pseudo-namestring language and in merge-pathnames* - should make quite a few pathnames things less ugly. (2.012.8) * Remember source-registry and output-translations parameters (2.012.8) - should provide a portable solution to the need many people have expressed to be able to tweak a configuration after the fact. * some documentation updates Possibly questionable change: * To support Genera, I removed ~@< from our error message format strings. Frankly, I think cuteness matters that much when printing error. Feedback requested: * are the (currently unexported) variables *source-registry-parameter* and *output-translations-parameter* acceptable APIs for reconfigurability of ASDF? If so, I'll export them before release. If not, I'd appreciate API proposals, if possible from people who understand how current code works. ASDF is pretty stable, and we're really polishing corner cases, but also making some [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Give up all hope for a better yesterday, even a better just now. Never give up hope for a better tomorrow. — Patri Friedman

4 13

[asdf-devel] ASDF2: run-shell-command for clisp: what is the correct :output?
by Mirko Vukovic 22 Feb '11

22 Feb '11

Hello, The asdf:run-shell-command for clisp is specified to use the output as terminal. That makes its output unavailable to clisp. Instead, one should have something like this: (read (ext:run-shell-command command :output :stream :wait t)) I am cross-posting this to the clisp mailing list. Folks there know much more about this than I do. Mirko

2 1

[asdf-devel] Minor simplification
by Juan Jose Garcia-Ripoll 06 Feb '11

06 Feb '11

Right now there are hooks in ASDF which are used by ECL in a perhaps too complicated way. More precisely, ECL requires to make an object file and a FASL file out of every compiled file, so that other operations (LOAD-FASL-OP, monolithic building, standalone executables, etc) become easier. Right now this is done using an :AFTER method on PERFORM. I suggest this patch (already in ECL's tree) which removes that method, removes the upgradability hacks and insteads wraps around COMPILE-FILE* (which now becomes redefinable at run time). Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

3 14

[asdf-devel] Issues with logical pathnames in Allegro and clisp
by Pascal Costanza 25 Jan '11

25 Jan '11

Hi, I have encountered two more issues when trying to use ASDF 2 with logical pathnames in Allegro and clisp. I have the following logical pathname translations in Allegro and clisp respectively: #+allegro (setf (logical-pathname-translations "costanza") `(("**;*.fasl.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fasl" (lisp-implementation-type) (read-from-string (lisp-implementation-version)))) ("**;*.*.*" "/Users/costanza/**/*.*"))) #+clisp (progn (setq custom:*parse-namestring-ansi* t) (setf (logical-pathname-translations "costanza") `(("**;*.lib.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.lib" (lisp-implementation-type) (read-from-string (lisp-implementation-version)))) ("**;*.fas.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fas" (lisp-implementation-type) (read-from-string (lisp-implementation-version)))) ("**;*.*.*" "/Users/costanza/**/*.*")))) When compiling systems with ASDF, however, the fasl, lib and fas files don't end up in the folders designated by these logical pathname translations, but rather in the locations as specified with ASDF output translations. (In CMUCL, Clozure, ECL, LispWorks, RMCL, and SBCL, similar logical pathname translations work as expected.) I have not defined any ASDF output translations of my own, but I'm using quicklisp, which probably does this. Please let me know if I can do something to help fixing this problem. Thanks, Pascal -- Pascal Costanza, mailto:pc@p-cos.net, http://p-cos.net Vrije Universiteit Brussel Software Languages Lab Pleinlaan 2, B-1050 Brussel, Belgium

3 6

[asdf-devel] ASDF with RMCL?
by Pascal Costanza 23 Jan '11

23 Jan '11

Hi, It seems that ASDF 2.x doesn't work with RMCL (ASDF 1.x did). Is that a known issue? Best, Pascal -- Pascal Costanza, mailto:pc@p-cos.net, http://p-cos.net Vrije Universiteit Brussel Software Languages Lab Pleinlaan 2, B-1050 Brussel, Belgium

4 16

[asdf-devel] ASDF 2.012
by Faré 03 Jan '11

03 Jan '11

I finally released ASDF 2.012, which is 2.011.9 being blessed. Since the previous release 2.011, there have been several minor improvements. Nothing serious or urgent, as ASDF 2 is getting mature, but it would be great if implementations were to update their version of ASDF to this latest release. Changes: Added :here directive to pathname DSL, robustified ECL support, fixed infinite loop when filesystem clock is in the future, extended the AOT DSL and made it more futureproof, fixed how clear-system interacts with map-systems, fixed use of directory under old SBCLs, fixed run-shell-command status and version string under clisp, fixed error messages. In the master (development) branch, I committed further cleanups as 2.012.1. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] For pretty much every writer, the big problem isn't piracy, it's obscurity. — Tim O'Reilly, as cited by Cory Doctorow

1 0

[asdf-devel] creating a distribution using asdf
by Sam Steingold 31 Dec '10

31 Dec '10

Hi, How do I distribute an application built using asdf? Specifically, given file foo.lisp, I need the list of all the fasl files of all the files on which foo.lisp depends (+ foo.fasl) in the correct order of loading. Thanks! -- Sam Steingold (http://sds.podval.org/) on Ubuntu 10.04 (lucid) http://iris.org.il http://ffii.org http://memri.org http://jihadwatch.org http://palestinefacts.org http://openvotingconsortium.org I'd give my right arm to be ambidextrous.

2 3

[asdf-devel] asdf 2.012 to be released on dec 31.
by Faré 28 Dec '10

28 Dec '10

I intend to release asdf 2.012 on dec 31. Hopefully, it would be my last release, and I would push for it to be included in all implementations. It would be nice if you would test the latest asdf 2.011.x to work on your platform before I do, maybe even try our regression test suite. Windows testers are particularly sought, since none of the maintainers seem to use windows. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Always design a thing by considering it in its next larger context — a chair in a room, a room in a house, a house in an environment, an environment in a city plan. — Eliel Saarinen

3 3

[asdf-devel] New test and windows
by Robert Goldman 28 Dec '10

28 Dec '10

I pushed a new test for asdf:run-shell-command that I believe will not work on Windows. The first step should be to use reader switches to remove the test contents when running on Windows, but ideally we should supply some windows code to take the place of the posix code where appropriate. The current test relies on /usr/bin/true and /usr/bin/false to test how asdf:run-shell-command checks exit codes. To be honest, I don't even know if Windows commands /have/ exit codes! See tests/run-shell-command-test.script I suspect that this means no one is running these tests, since there hasn't been a loud cry of outrage!

3 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel