asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

[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

Re: [asdf-devel] Question about use of :unspecific
by Faré 17 Mar '10

17 Mar '10

On 17 March 2010 05:20, james anderson <james.anderson(a)setf.de> wrote: > > On 2010-03-17, at 02:50 , Faré wrote: > >> ECL & LispWorks work for me, > > that's nice. ecl has some sort of problem with the test mechanism[0], which > it does not have when i run the pathname tests as originally structured. > > in order to run lispworks in batch mode i must trash the x library and feed > the tests through stdin. that's a problem with their free version. > You should ask for a test license from LispWorks, then you can obtain the "lispworks" binary suitable for testing with, e.g. # echo '(hcl:save-image "lispworks" :environment nil)' > /tmp/build.lisp ; # ./lispworks-6-0-0-x86-linux -siteinit - -init - -build /tmp/build.lisp > i was hoping they would release something prebuilt in order that i can avoid > having to install the entire java dev world just in order to build abcl. > > their report must be missing some details: the leave-lisp operator is > missing a clause for abcl, which prevents the tests from running. it needs > something like > > #+abcl > (extensions:quit :status return) > > before they get off the ground. in any case, the transcript[1] reads as if > there is some problem with the test mechanics not with the test content. if > you have any insight into that aspect of the problem, that would help. > >> You can either export ASDF_OUTPUT_TRANSLATIONS= something >> or after loading asdf you can asdf:initialize-output-translations with >> a proper SEXP. > > what would a proper value be? one which still can claim to test asdf's > "normal" configuration? > In run-tests.sh I currently use export ASDF_OUTPUT_TRANSLATIONS="${asdfdir}:${asdfdir}/tmp/fasls/$(basename $command):" The whole point of that value is to short-circuit the "normal" configuration. But the last ":" in said variable is so you can still see said normal configuration when you print (asdf::output-translations). >> I'd be most happy if it [ASDF tests] converted to using Stefil or 5AM >> or some such thing, >> with proper asdf::*variable* rebinding and package deletion. >> But I'm probably not going to do it myself. > [0] : > http://ec2-174-129-63-37.compute-1.amazonaws.com/test/log/20100316T233422/e… > [1] : > http://ec2-174-129-63-37.compute-1.amazonaws.com/test/log/20100316T233422/a… [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Mathematicians are like lovers. Grant a mathematician the least principle, and he will draw from it a consequence which you must also grant him, and from this consequence another. — Bernard Le Bouyer de Fontenelle

2 1

[asdf-devel] Windows pathnames on ACL
by Robert Goldman 16 Mar '10

16 Mar '10

I don't see much that's helpful in the ACL manual http://preview.tinyurl.com/y8nfazw --- how user-homedir-pathname behaves on windows Beyond that, I'd suggest sending email to bugs(a)franz.com to ask for advice. For that matter, Gary King was kinda deputized to speak for Allegro in this forum. Gary, are you there? Could you help Faré dig up information about where to dump special files in Windows with ACL?

3 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel