asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] ASDF 2.23 ported to MKCL.
by Jean-Claude Beaudoin 27 Jul '12

27 Jul '12

Hello ASDF maintainers, I have done a port of ASDF 2.23 to MKCL that will be included in the next MKCL 1.1.0 release candidate. ASDF has been bundled with MKCL for a long while already but I think that, with 1.1.0, MKCL is now stable enough for the port of ASDF to MKCL to be usefully merged with the ASDF main development branch. The new ASDF 2.23 for MKCL code is available on github at: git://github.com/jcbeaudoin/asdf-mkcl.git I hope you will find convenient enough to pull from it the relevant parts for the merge. Regards, Jean-Claude Beaudoin

2 1

Re: [asdf-devel] ECL tests failing on Mac OS X Lion [Re: asdf 2.23 released]
by Robert Goldman 24 Jul '12

24 Jul '12

On 7/17/12 Jul 17 -12:05 PM, Faré wrote: > On Tue, Jul 17, 2012 at 12:42 PM, Robert Goldman <rpgoldman(a)sift.info> wrote: >> I tried running the tests on the latest ASDF, using the ECL that one >> gets from Mac Ports (on Lion). I got a number of test failures. >> >> test-module-depend failed >> test-module-excessive-depend failed >> test-multiple failed >> test-retry-loading-component-1 went into an infinite loop, catching an >> error and restarting over and over. >> >> I'll collect more information as I can, but thought I should give the >> update. >> > Works for me on Linux x64, using ECL (Embeddable Common-Lisp) 11.1.1 > (git:78442fa7bcb4ef486b704e16d0e7cefbd4bf7680). I have 12.2.1 from Mac Ports. Looks like there might be some packaging problem in how MacPorts ships/installs ECL: test-module-depend: .... ;;; Loading "/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas" LOAD: Could not load file #P"/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas" (Error: "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, 10): Library not loaded: /opt/local/lib/libffi.5.dylib Referenced from: /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas No reason obvious to me that loading test/file3.lisp should cause ECL to want to load libffi.... Yes, this seems like a packaging/dependency error. I don't have libffi.5.dylib --- I have libffi.6.dylib. When I ask port what ecl depends on, it says "nothing," so presumably there's an error, and it should specify a dependency on libffi. Juanjo, do you have any contact with the MacPorts people? I'm not sure how to report this as a bug.... thanks, r

4 7

[asdf-devel] asdf 2.23 released
by Faré 19 Jul '12

19 Jul '12

I am pleased to announce the release of ASDF 2.23. Since previous release 2.22, the changes are as follow: * add new :compile-check argument to compile-file* and around-compile-hook. This allows for consistency check of .fasl output before the file can possibly be seen by other builds (i.e. no race condition). This change makes the asdf-finalizers extension possible. * export more utilities for dealing with pathnames from environment. These changes are few and subtle, but nonetheless significant to those who'd use these features. As usual, developers, please test and enjoy, vendors, please update your implementation or distribution. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org A tautology is a thing which is tautological.

3 2

[asdf-devel] mailing list admin...
by Robert Goldman 07 Jul '12

07 Jul '12

I responded to the earlier message about the ASDF system recompilation, but from an alternative email address, so the email went to the moderator. Does anyone know who IS the moderator these days? Last time I checked it was Gary King.... Cheers, r

2 1

[asdf-devel] recompiling a system when depency system changed
by Anton Vodonosov 07 Jul '12

07 Jul '12

Hello. I have a local project, it's ASDF system specifies :depends-on (#:fiveam ...) The recent quicklisp delivers new version of fiveam. But when my program performed asdf:load-op on that system, the system didn't get recompiled, and old .fasl files are loaded (with error, because they become incompatible). Is it expected behaviour of ASDF or should I dig more and isolate the problem in reproducible test case? Best regards, - Anton

3 4

[asdf-devel] asdf 2.23, and contribs
by Faré 05 Jul '12

05 Jul '12

Dear fellow lispers, I'd like to release asdf 2.23 around July 14 or so. Can you review the changes so far and test it for stability? Changes since 2.22: * exported more pathname-related utilities from the package asdf * tweak compile-file* to accept a :compile-check argument, and the :around-compile protocol to allow passing flags to compile-file* This allows for a race-condition-free way of imposing strictures on files that are being compiled, and is used by asdf-finalizers. Speaking of which, some time ago, I started to collect asdf extensions, and I just added a listing of them on the asdf webpage. Please suggest more extensions that I may list on the page. Currently listed are: * asdf-contrib, an umbrella that just depends-on other extensions. * asdf-encodings (depends on asdf 2.21), to compile Lisp source files with character encodings other than UTF-8. * asdf-bundle, to bundle one or more systems into a single FASL file, for easier delivery (only on SBCL, CCL and hopefully still ECL, for now). * asdf-condition-control (distributed as part of XCVB), to control which conditions to warn about or to muffle during compilation. * asdf-finalizers, to allow macros, reader-macros or types to include code to be evaluated at the toplevel, at the end of a file being compiled. (I personally think it's very cool.) * asdf-dependency-grovel, to compute the actual dependencies in a big ASDF system (not included by asdf-contrib). * poiu, to compile a system in parallel (not included by asdf-contrib). I suppose I should list CFFI and IOlib (and possibly SB-GROVEL?), maybe cl-protobufs, xcvb-bridge and more, for notably possessing non-trivial ASDF extensions. Or should I? What other systems should I list? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. — William Pitt, 1783

2 1

[asdf-devel] asdf 2.22 released
by Faré 16 Jun '12

16 Jun '12

I am pleased to announce the release of ASDF 2.22. Since previous release 2.21, the changes are as follow: * require is now mapped to the recently defined require-system, not to load-system anymore. * more sensible inheritance semantics for default-component-class, which can be either a class or a class name. (hat tip to Nikodemus) * accept wildcards in directory-files for physical pathnames. (hat tip to Erik Pearson). These changes are few and subtle, but nonetheless significant to those who'd use these features. As usual, developers, please test and enjoy, vendors, please update your implementation or distribution. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Of course, Third World leaders love you. By ascribing third world ills to First World sins, you absolve them of blame for their countries' failure to advance. — John McCarthy

2 3

[asdf-devel] asfd:implementation-identifier is public on SBCL but private in CLISP
by Anton Vodonosov 03 Jun '12

03 Jun '12

Hello. On SBCL I can access asff:implentation-identifier, but on CLISP i can't. Only asff::implentation-identifier works. Is it OK? ASDF 2.014.6. Best regards, - Anton

2 3

[asdf-devel] toward asdf 2.22
by Faré 03 Jun '12

03 Jun '12

Is anyone working on asdf or desiring a fix to any known bug? Otherwise, I'd like to promote current asdf HEAD (2.21.5) as a release candidate, that Erik Pearson and Nikodemus Siivola might enjoy the improvements done for them. Changes: * require is now mapped to the recently defined require-system, not to load-system anymore. * more sensible inheritance semantics for default-component-class, which can be either a class or a class name. * accept wildcards in directory-files for physical pathnames. —♯ƒ • 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

1 0

[asdf-devel] Various issues
by Tobias C Rittweiler 24 May '12

24 May '12

Hi there! Thanks to the ASDF maintainers. I just visited ASDF's website on common-lisp.net since a long time, and it makes a nicely maintained impression! Well done. I have the following issues: * The rather old ASDF version that I'm using ("2.010") does not seem to be able to cope with multiple :depends-on clauses. (Only one clause seems to be used.) Is this intended behaviour? Might it be fixed in more recent versions? * :STATIC-FILE (and :FILE for that matter) are not discussed or explained in the manual. * We generate a 'version.lisp' with a (DEFPARAMETER ...) form in it when using "make" to build a Lisp binary using buildapp. Is there a component that loads a file if it exists and if it does not exist just skips the clause? Thanks, T

4 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel