[Asdf-devel] ASDF 3.1.4.1 (non-release) pushed

This has a bug-fix for MKCL and some minor tweaks to the internal tools (not visible to most of you) and tests. Bug-reports and test results welcome. Cheers, r ___ Asdf-devel mailing list Asdf-devel@common-lisp.net http://mailman.common-lisp.net/cgi-b

Re: [Asdf-devel] ASDF test failure on MKCL linux

Jean-Claude Beaudoin wrote: > > On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman > wrote: > > Jean-Claude Beaudoin wrote: > > > > On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman > mailto:rpgold...@sift.info> > >

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman wrote: > Jean-Claude Beaudoin wrote: > > > > On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman > > wrote: > > > > > > This morning I pulled an update from the mkcl git repo, rebuilt on my > > Linux Mint machin

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman wrote: > What happens here is that there is a function with undeclared local > variables, but ASDF is not getting a warning from COMPILE-FILE, so it > mistakenly believes the build is successful. > > I don't think I wrote this test properly, thoug

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman wrote: > Jean-Claude Beaudoin wrote: > > > > On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman > > wrote: > > > > > > This morning I pulled an update from the mkcl git repo, rebuilt on my > > Linux Mint machin

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Mon, Nov 3, 2014 at 11:28 PM, Robert P. Goldman wrote: > > Actually, we pulled lisp-invocation into ASDF as a git submodule (it was > liberated from XCVB). You should get this lisp invocation automatically. > > Please go to your ext/ subdirectory and populate the git submodules > there, and t

Re: [Asdf-devel] ASDF test failure on MKCL linux

Jean-Claude Beaudoin wrote: > > On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman > wrote: > > > This morning I pulled an update from the mkcl git repo, rebuilt on my > Linux Mint machine, and retested with the latest ASDF. All the tests > that completed

Re: [Asdf-devel] ASDF test failure on MKCL linux

Jean-Claude Beaudoin wrote: > I think I just found out the environmental discrepancy between your > setup and mine. > test-program.script depends on system :lisp-invocation from XCVB and > will happily skip over the whole test if that demand is not satisfied. > XCVB is not currently part of my rea

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Mon, Nov 3, 2014 at 8:30 PM, Jean-Claude Beaudoin wrote: > cd asdf; make t l=mkcl > > This resulted in: > > -#--- > Using /home/jean-claude/tmp/ASDF/mkcl/src/bin/mkcl > Ran 56 tests: > 55 passing and 1 failing > failing test(s): test-undeferred-warnings.sc

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman wrote: > > This morning I pulled an update from the mkcl git repo, rebuilt on my > Linux Mint machine, and retested with the latest ASDF. All the tests > that completed seemed to complete successfully, but test-program.script > hung, instead of c

Re: [Asdf-devel] ASDF test failure on MKCL linux

Jean-Claude Beaudoin wrote: > > On Sun, Oct 5, 2014 at 11:03 PM, Faré > wrote: > > test-try-refinding.script is a relatively new test (introduced shortly > before the 3.1.3 release), so its failure might not be a regression in > ASDF if none of us tested 3.1.

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

Faré wrote: : rpg >>> : fare >> : rpg > >>> You're discussing the behavior of a file that isn't checked in; >> No, this file is checked in, and you should see these results if you run >> the test suite after pulling master from cl.net. >> > OK, I might have been looking at the wrong plac

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

>>>: rpg >>: fare >: rpg >>> How do you distinguish between the build failing and succeeding but >>> being followed by an error signal? >>> >> Nothing in ASDF should cause an error signal at the end of the W-C-U. > > I think I'm misunderstanding the following from your previous message: > > "if d

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

Faré wrote: > On Wed, Oct 29, 2014 at 11:40 PM, Robert P. Goldman > wrote: >> #P"/Users/rpg/lisp/asdf/build/fasls/sbcl-1.2.0-macosx-x64/asdf/test/fun-with-undefined-locals.fasl" >> >> ; file: /Users/rpg/lisp/asdf/test/fun-with-undefined-locals.lisp >> ; in: DEFUN FUN-WITH-UNDEFINED-LOCALS-PACKAGE

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

On Wed, Oct 29, 2014 at 11:40 PM, Robert P. Goldman wrote: > #P"/Users/rpg/lisp/asdf/build/fasls/sbcl-1.2.0-macosx-x64/asdf/test/fun-with-undefined-locals.fasl" > > ; file: /Users/rpg/lisp/asdf/test/fun-with-undefined-locals.lisp > ; in: DEFUN FUN-WITH-UNDEFINED-LOCALS-PACKAGE::FOO > ; (+ FUN-

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

avior introduced by >>> recent changes to SBCL, and I'm not on the latest release yet. >> Very strange. I can reproduce the problem with all the SBCL versions I >> have: 1.1.4, 1.1.18, 1.2.4. SBCL 1.2.4 includes the latest version of >> ASDF. Do you see any differenc

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

you see any difference in behavior between deferred and normal > warnings, i.e. (defun foo () (+ a b)) vs (defun foo () (foo 3))? > > _______ > Asdf-devel mailing list > Asdf-devel@common-lisp.net > http://mailman.common-lisp.net/cgi-bin/mailman/listin

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

I figured out my problem: my code was not calling (enable-deferred-warnings-check). Sorry for the noise. I was not even aware of ENABLE-DEFERRED-WARNINGS-CHECK. What is the reason for suppressing defer-able warnings by default? As far as I understand the distinction between normal and deferred war

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

"Robert P. Goldman" writes: > I cannot replicate this, but this may be a new behavior introduced by > recent changes to SBCL, and I'm not on the latest release yet. Very strange. I can reproduce the problem with all the SBCL versions I have: 1.1.4, 1.1.18, 1.2.4. SBCL 1.2.4 includes the latest ve

Re: [Asdf-devel] ASDF does not signal deferred non-style warnings as an error

Ilya Perminov wrote: > Hi, > > ASDF does not raise an error, when the SBCL compiler produces > warnings (e.g. "undefined variable", "undefined function"). > Example: > test.asd = > (defsystem :test > :version "1.0" > :components ((:file "test"))) > test.lisp

[Asdf-devel] ASDF does not signal deferred non-style warnings as an error

Hi, ASDF does not raise an error, when the SBCL compiler produces warnings (e.g. "undefined variable", "undefined function"). Example: test.asd = (defsystem :test :version "1.0" :components ((:file "test"))) test.lisp (defun foo () (+ a b)) ==

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Sun, Oct 5, 2014 at 11:03 PM, Faré wrote: > test-try-refinding.script is a relatively new test (introduced shortly > before the 3.1.3 release), so its failure might not be a regression in > ASDF if none of us tested 3.1.3 with MKCL (did we?). Now, infinite > looping is certainly a bad failure

Re: [Asdf-devel] ASDF 3.1.4 released today

On Sat, Oct 11, 2014 at 1:24 PM, Kambiz Darabi wrote: >> 1- When you comment out (--git-upstream-tag="%(version)s"), which tree >> does it use as upstream? The current one? I suppose that will work. > It uses upstream/3.1.4. I renamed the upstream origin to point at my > github fork. > OK. So you

Re: [Asdf-devel] ASDF 3.1.4 released today

Hi Faré, On 2014-10-11 16:55 CEST, Faré wrote: > Looking at your patch > https://github.com/darabi/asdf/commit/3e57db9e1e3488ed0269ea1d301fa29f0b83ed4e > > 1- When you comment out (--git-upstream-tag="%(version)s"), which tree > does it use as upstream? The current one? I suppose that will work.

Re: [Asdf-devel] ASDF 3.1.4 released today

Looking at your patch https://github.com/darabi/asdf/commit/3e57db9e1e3488ed0269ea1d301fa29f0b83ed4e 1- When you comment out (--git-upstream-tag="%(version)s"), which tree does it use as upstream? The current one? I suppose that will work. 2- What does --git-submodule do? Is it supposed to includ

Re: [Asdf-devel] ASDF 3.1.4 released today

On Sat, Oct 11, 2014 at 6:47 AM, Kambiz Darabi wrote: >> [...] I recommend you don't bother with the scripts in master, and >> instead use the tools in the minimakefile branch, due to be merged >> RSN. > > Yes, with those tools and the change in [1] it was a breeze. Thank you! > I hope Robert wil

Re: [Asdf-devel] ASDF 3.1.4 released today

Hi Faré, On 2014-10-11 04:20 CEST, Faré wrote: > On Fri, Oct 10, 2014 at 6:53 PM, Kambiz Darabi wrote: > [...] > Mind that the correct release script is in the minimakefile branch, > that I believe Robert is evaluating for merge into master. > Also mind that said release script is too dumb to h

Re: [Asdf-devel] ASDF 3.1.4 released today

Dear Kambiz, On Fri, Oct 10, 2014 at 6:53 PM, Kambiz Darabi wrote: > thank you for packaging and uploading again. I didn't notice that you > have already performed the build and uploaded to mentors until I came to > the uploading step. > Oops, I didn't know you were on it. Thanks for trying. Next

Re: [Asdf-devel] ASDF 3.1.4 released today

g fixes, to Dave Cooper for testing, and all > who reported bugs and provided patches. > > Best, > R > > ___ > Asdf-devel mailing list > Asdf-devel@common-lisp.net > http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel

[Asdf-devel] ASDF 3.1.4 released today

This is a maintenance and bugfix release. There should be no incompatibilities, and many small fixes. The one new feature is an optional speedup to system search. Users who have large directory trees to search, and stable sets of systems, can build a system search cache that will substantially sp

Re: [Asdf-devel] ASDF test failure on MKCL linux

Faré wrote: > On Mon, Oct 6, 2014 at 5:38 PM, Robert Goldman wrote: >> After disabling test-try-refinding, I get two more test failures on MKCL: >> >> test-program: >> >> ; Registering # >> TEST ABORTED: Error while trying to load definition for system >> hello-world-example from pathname /home/rp

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Mon, Oct 6, 2014 at 5:38 PM, Robert Goldman wrote: > After disabling test-try-refinding, I get two more test failures on MKCL: > > test-program: > > ; Registering # > TEST ABORTED: Error while trying to load definition for system > hello-world-example from pathname /home/rpg/common-lisp/asd\ >

Re: [Asdf-devel] ASDF test failure on MKCL linux

After disabling test-try-refinding, I get two more test failures on MKCL: test-program: ; Registering # TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOG

Re: [Asdf-devel] ASDF test failure on MKCL linux

Jean-Claude Beaudoin wrote: > > On Sun, Oct 5, 2014 at 11:03 PM, Faré > wrote: > [...snip...] > > If I replace the culprit loop (just before (DBG "Refinding test > successful.")) by this debugging variant, I find that the variable > tried-once is somehow mag

Re: [Asdf-devel] ASDF test-program failure, clisp Mac OS X

On Mon, Oct 6, 2014 at 3:20 PM, Robert P. Goldman wrote: > Interestingly, this fails for me, too, but with a different error -- I > get a mismatch which looks like the image ran, but I got the REPL prompt > in the output, instead of just the output alone: > > These two expressions fail comparison

[Asdf-devel] ASDF test-program failure, clisp Mac OS X

Interestingly, this fails for me, too, but with a different error -- I get a mismatch which looks like the image ran, but I got the REPL prompt in the output, instead of just the output alone: These two expressions fail comparison with EQUAL: (NEST (LISP-INVOCATION:INVOKE-LISP :CROSS-COMPILE NIL

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Sun, Oct 5, 2014 at 11:03 PM, Faré wrote: > test-try-refinding.script is a relatively new test (introduced shortly > before the 3.1.3 release), so its failure might not be a regression in > ASDF if none of us tested 3.1.3 with MKCL (did we?). Now, infinite > looping is certainly a bad failure

Re: [Asdf-devel] ASDF test failure on MKCL linux

test-try-refinding.script is a relatively new test (introduced shortly before the 3.1.3 release), so its failure might not be a regression in ASDF if none of us tested 3.1.3 with MKCL (did we?). Now, infinite looping is certainly a bad failure mode in the test. This looks like a MKCL-specific bug,

Re: [Asdf-devel] ASDF test failure on MKCL linux

ror, and >>> this time test-retry-loading-component-1 *also* failed: >>> >>> TEST ABORTED: Error while trying to load definition for system >>> hello-world-example from pathname /home/rpg/common-lisp/asd\ >>> f/test/hello-world-example.asd: Unknown initialization option >>> :EPILOGUE-CODE for class #>> 6> >>> >>> Cheers, >>> r >>> >>> >>> >>> Tried updating my mkcl from git and that failed to build on linux: >>> sed '/-CUT-/,$d' ./mkcl/config.h > ./mkcl/config-install.h >>> /bin/bash: ./mkcl/config-install.h: Permission denied >>> make[1]: *** [mkcl/config-install.h] Error 1 >>> make[1]: Leaving directory `/home/rpg/src/mkcl/src' >>> make: *** [all] Error 2 >> >> >> ___ >> Asdf-devel mailing list >> Asdf-devel@common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel >> ___ Asdf-devel mailing list Asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel

Re: [Asdf-devel] ASDF test failure on MKCL linux

On Sun, Oct 5, 2014 at 8:57 PM, Faré wrote: > Dear JCB, > > You suggestion indeed fixes test-bundle.script, but now > this test loops indefinitely for me, using the latest mkcl from git: > make t l=mkcl t=test-try-refinding.script > > This one does not look like a mere typo. I will have to invest

Re: [Asdf-devel] ASDF test failure on MKCL linux

>> >> TEST ABORTED: Error while trying to load definition for system >> hello-world-example from pathname /home/rpg/common-lisp/asd\ >> f/test/hello-world-example.asd: Unknown initialization option >> :EPILOGUE-CODE for class #> 6> >> >> Cheers, >

Re: [Asdf-devel] ASDF test failure on MKCL linux

Somehow, what I suspect to be a typo has been introduced in the test-bundle.script in the form of a "MKEXT" package name. MKCL never had a "MKEXT" package but it has a "MK-EXT" package nickname for package "MKCL". The "MK-EXT" nickname is to mimic the "SB-EXT" package in SBCL. So you should either

[Asdf-devel] ASDF test failure on MKCL linux

test-bundle failed for me, on version 1.1.9 of MKCL: Now for the mono-fasl TEST ABORTED: There is no package with the name MKEXT. 0: (# #) 1: (# #) 2: (# #) 3: (# #) 4: (# ((ASDF-TEST::ARGS # :COUNT 69 :STREAM #) (ASDF-TEST::NAME . :PRINT-CONDITION-BACKTRACE) (#:|%the-lock--28954-510| . #) (#:|%

Re: [Asdf-devel] ASDF Release?

Faré wrote: > Dear Anton, dear Robert, dear Common Lisp hackers, > > since 3.1.3 in last July there have been many minor bug fixes to ASDF > and UIOP (plus enhancements for ECL, GCL, LispWorks, MKCL), a > .cl-source-registry.cache feature for faster script startup, and > slight documentation impro

[Asdf-devel] ASDF Release?

Dear Anton, dear Robert, dear Common Lisp hackers, since 3.1.3 in last July there have been many minor bug fixes to ASDF and UIOP (plus enhancements for ECL, GCL, LispWorks, MKCL), a .cl-source-registry.cache feature for faster script startup, and slight documentation improvements. I believe it's

Re: [Asdf-devel] ASDF

Faré wrote: > Dear Geoff, > >>> If you are still interested in becoming ASDF maintainer, which I hope >>> you are, or even just developer, here is a post linking to some >>> suggested things to read about the state of ASDF: >>> http://fare.livejournal.com/176185.html >> I am still interested, even

Re: [Asdf-devel] ASDF

Dear Geoff, >> If you are still interested in becoming ASDF maintainer, which I hope >> you are, or even just developer, here is a post linking to some >> suggested things to read about the state of ASDF: >> http://fare.livejournal.com/176185.html > > I am still interested, even enthusiastic. I w

Re: [Asdf-devel] ASDF and generated files

Hi, Ralf -- I think that the advice you have gotten from Fare and Robert Brown agrees with my experience (with another application that involves a translation from some alternate input form to common lisp source). I have been working on an article for ILC that would describe how to extend the ASD

Re: [Asdf-devel] ASDF and generated files

On Thu, 14 Aug 2014 13:41:05 -0400, Faré wrote > Dear Ralf, Hello, > congratulations for maintaining Common Music! > How does it compare to OpenMusic, these days? Oh no, I'm not maintaining the current Common Music (v3). I'mk trying to keep Common Music v2 in an operational shape (CMv3/Grace mov

Re: [Asdf-devel] ASDF and generated files

___ > Asdf-devel mailing list > Asdf-devel@common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel ___ Asdf-devel mailing list Asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel

Re: [Asdf-devel] ASDF and generated files

heme > file to lisp (Common Music's scheme->lisp compiler works on files). > > TIA Ralf Mattes > > Footnotes: > [1] my main goal is to make Common Music distributable by quicklisp. > > > __

[Asdf-devel] ASDF and generated files

Hello, dear ASDF developers, I'm currently trying to port some old lisp code (Common Music) to ASDF3[1]. Common Music's source is written in Scheme, the Common Lisp version is generated from the Scheme code. Unfortunately CM's current asdf file is littered with executable code (not only compiling

[Asdf-devel] ASDF version 3.1.3 released: Important bug-fix release

Today I have released (with much help from Fare) ASDF 3.1.3. We urge implementations that are currently shipping with 3.1.2 to move forward to 3.1.3. 3.1.3 has no API incompatibilities that we know of, and contains significant bug fixes. Most significantly, 3.1.3 fixes bugs that impede hot-upgra

Re: [Asdf-devel] ASDF 3.1.2.9 now available

Mark Evenson wrote: > On 17 Jul 2014, at 04:43, Anton Vodonosov wrote: > >> I've run cl-test-grid tests on several lisps. >> >> No regressions detected. >> >> The lisps tested: >> abcl-1.2.1-fasl42-linux-x86 >> abcl-1.3.1-fasl42-linux-x86 > > abcl-1.4.0-dev has been updated to this ASDF. > Tha

Re: [Asdf-devel] ASDF 3.1.2.9 now available

On 17 Jul 2014, at 04:43, Anton Vodonosov wrote: > I've run cl-test-grid tests on several lisps. > > No regressions detected. > > The lisps tested: > abcl-1.2.1-fasl42-linux-x86 > abcl-1.3.1-fasl42-linux-x86 abcl-1.4.0-dev has been updated to this ASDF. -- "A screaming comes across the sky.

Re: [Asdf-devel] ASDF 3.1.2.9 now available

_ > Asdf-devel mailing list > Asdf-devel@common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel ___ Asdf-devel mailing list Asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel

[Asdf-devel] ASDF 3.1.2.9 now available

We have merged the bug fixes for 1335323, and pushed as 3.1.2.9. This is a release candidate for 3.1.3, which we hope to release this coming week. Please test it! thanks! r ___ Asdf-devel mailing list Asdf-devel@common-lisp.net http://common-lisp.net/

Re: [Asdf-devel] asdf and dependencies

Hi Faré, yes, definitely. I was on a business travel and had little time, but now I'm back and seeing the light at the end of the tunnel. I will create such a repo shortly and update you. Cheers Kambiz On 2014-07-08 21:46 CEST, Faré wrote: > Dear Kambiz, > > are you still interested in maki

[Asdf-devel] asdf and dependencies

Dear Kambiz, are you still interested in making a git repository with asdf + dependencies as modules? It would help development and make Robert more comfortable with the minimakefile branch. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Do not handicap your childr

Re: [Asdf-devel] [asdf-devel] Make the CL syntax predictable

ategory of history in 10 years, meaning that a significant number > of people will still use it to develop new software, then i'll be both > surprised and disappointed. I know people who work with PL/I till now; and even more people who use C++. I don't worry

Re: [Asdf-devel] [asdf-devel] Backward incompatible improvements

30.03.2014, 05:29, "Daniel Herring" : > On Sat, 29 Mar 2014, Anton Vodonosov wrote: > >>  29.03.2014, 02:39, "Daniel Herring" : >>>  Would it be possible to have a special header in asdf files indicate that >>>  the contained system(s) should be loaded using the new syntax mechanism? >>> >>>  [...]

[asdf-devel] asdf/bundle and ECL prologue / epilogue

Is anyone at all using asdf-bundle with ECL? It looks like the prologue and epilogue support were casualties of some operation canonicalization. Also, the way the flags are or aren't propagated to sub-operations is misdesigned. Finally, it seems like prologue and epilogue ought to be part of the s

Re: [asdf-devel] asdf loading error error

On Sun, Feb 23, 2014 at 11:27 AM, Robert Goldman wrote: >> There's an error while reporting a warning (warning about your system >> having a bad version string). >> I suggest you add this method in system.lisp after defclass system: >> (defmethod builtin-system-p ((x null)) nil) >> Does it help?

Re: [asdf-devel] asdf loading error error

Could this be the BUILT-IN-SYSTEM-P check? Faré recently added this block to the code for wrangling system versions: (let ((sysfile (system-source-file (component-system component (when (and (typep component 'system) (not bspp)) (setf (builtin-system-p component) (lis

Re: [asdf-devel] asdf loading error error

OK, so that's why there's a bad version error. I get that. Would it be a big problem to fix the system instead of trying to fix ASDF? That still doesn't answer my original question: what's this about the built-system-p check? Why does that need fixing?

Re: [asdf-devel] asdf loading error error

On 2/23/14, 17:27, Robert Goldman wrote: > Faré wrote: >> On Sat, Feb 22, 2014 at 3:26 PM, Cyrus Harmon wrote: >>> While trying to load and asdf system that generates an error (that’s >>> another story, presumably an abcl-contrib problem), I get the following >>> error: >>> >>> Error while tryin

Re: [asdf-devel] asdf loading error error

Faré wrote: > On Sat, Feb 22, 2014 at 3:26 PM, Cyrus Harmon wrote: >> While trying to load and asdf system that generates an error (that’s another >> story, presumably an abcl-contrib problem), I get the following error: >> >> Error while trying to load definition for system abcl-cdk from >> path

Re: [asdf-devel] asdf loading error error

On Sat, Feb 22, 2014 at 3:26 PM, Cyrus Harmon wrote: > > While trying to load and asdf system that generates an error (that’s another > story, presumably an abcl-contrib problem), I get the following error: > > Error while trying to load definition for system abcl-cdk from > pathname /Users/sly/p

[asdf-devel] asdf loading error error

While trying to load and asdf system that generates an error (that’s another story, presumably an abcl-contrib problem), I get the following error: Error while trying to load definition for system abcl-cdk from pathname /Users/sly/projects/abcl-cdk/abcl-cdk.asd: There is no applicable method

Re: [asdf-devel] ASDF 3.0.3 ported to MKCL 1.1.7

On Thu, Feb 20, 2014 at 9:09 PM, Faré wrote: > > while you're at it, beside making it work with the latest 3.1, > you can look at the ECL-only tests and mkcl workarounds in the tests > (grep for ecl and mkcl tests/ and subdirectories). > It would be great if you could make them work on MKCL, too.

Re: [asdf-devel] ASDF 3.0.3 ported to MKCL 1.1.7

On Thu, Feb 20, 2014 at 7:23 PM, Faré wrote: > On Wed, Feb 19, 2014 at 10:02 AM, Robert P. Goldman > wrote: > > Jean-Claude Beaudoin wrote: > >> > >> 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

Re: [asdf-devel] ASDF 3.0.3 ported to MKCL 1.1.7

Dear JCB, while you're at it, beside making it work with the latest 3.1, you can look at the ECL-only tests and mkcl workarounds in the tests (grep for ecl and mkcl tests/ and subdirectories). It would be great if you could make them work on MKCL, too. test-bundle and test-program notably are like

Re: [asdf-devel] ASDF 3.0.3 ported to MKCL 1.1.7

On Wed, Feb 19, 2014 at 10:02 AM, Robert P. Goldman wrote: > Jean-Claude Beaudoin wrote: >> >> 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

Re: [asdf-devel] ASDF 3.0.3 ported to MKCL 1.1.7

Jean-Claude Beaudoin wrote: > > 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 > the

[asdf-devel] ASDF 3.0.3 ported to MKCL 1.1.7

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

Re: [asdf-devel] ASDF walkthrough

I'm definitely in. Sent from my iPad > On Jan 3, 2014, at 1:10, Faré wrote: > > Dear Lisp hackers, > > I'm considering recording a walk through the ASDF sources. > > I'd like to have an interactive session over Google Hangout > with one or a few people, explaining the current code in asdf/def

Re: [asdf-devel] ASDF walkthrough

Excellent idea! Please let me know when you will be doing this. Currently, I would possibly profit from an explanation of the kinds of "transversal" ASDF does over the "system of systems" it needs to do, but that is not too sharply defined  as a question yet. Tersely pecked on my Nexus 5 On Ja

[asdf-devel] ASDF walkthrough

Dear Lisp hackers, I'm considering recording a walk through the ASDF sources. I'd like to have an interactive session over Google Hangout with one or a few people, explaining the current code in asdf/defsystem (i.e. not going into uiop, except to minimally explain what asdf uses). That should tak

[asdf-devel] ASDF testing for 3.1.0.24 begins...

Running tests against 3.1.0.24. So far we have a failure for abcl on Windows. I plan to put all my asdf test failures here from now on: https://www.dropbox.com/home/Public/asdf-failures I'll try to send notifications when something new lands in there. Will it be useful to post the non-failu

[asdf-devel] ASDF 3.0.3 released

Dear Lisp hackers, I am pleased to announce the release of ASDF 2.26. Since previous release 2.25, the changes are as follows: * Run-program much improved, with a slight backward incompatibility. See the new documentation about it. * Portability enhanced, with more robust Windows support,

[asdf-devel] ASDF testing for LWW

Hi, I've been helping with ASDF regression testing on Windows, where we use a cygwin shell to run the ASDF test scripts. We don't have LispWorks licensed for Windows currently, so I looked at using the Personal Edition. But this is apparently not possible because the ASDF tests assume a "console

[asdf-devel] ASDF, primary-system-name and Quicklisp

Dear Common Lispers, Zach reminds me that one thing is blocking his upgrading the ASDF in Quicklisp is the fact that currently, every user-defined function in *system-definition-search-functions* currently has to be aware of ASDF 3's primary-system-name feature, or it may fail to properly extend A

Re: [asdf-devel] ASDF

On Sun, Sep 29, 2013 at 10:00 PM, Robert P. Goldman wrote: > I'm hoping to be able to pull in your run-program branch altogether. > Oh, excellent! I just pushed some more documentation on that branch, together with a slight tweak for *standard-readtable* (the use of which around reading .asd files

Re: [asdf-devel] ASDF

Faré wrote: > I suppose it would be better to release 3.0.3 without merging my > branches, and merge my branches afterwards. On the other hand, there > are a few bugs I fixed in my run-program branch, independently from > the new functionality, that I'd like to commit in the master branch > before

[asdf-devel] ASDF

I suppose it would be better to release 3.0.3 without merging my branches, and merge my branches afterwards. On the other hand, there are a few bugs I fixed in my run-program branch, independently from the new functionality, that I'd like to commit in the master branch before the release, with your

Re: [asdf-devel] ASDF 3.0.2.1 released

Thank you very much for the clarifications. I will fix up the documentation accordingly. Best, R Sent from my iPad On Jul 31, 2013, at 17:44, Faré wrote: > On Wed, Jul 31, 2013 at 3:45 PM, Robert Goldman wrote: >> Will do. I didn't get around to documenting RECYCLE per our >> conversation

Re: [asdf-devel] ASDF 3.0.2.1 released

On Wed, Jul 31, 2013 at 3:45 PM, Robert Goldman wrote: > Will do. I didn't get around to documenting RECYCLE per our > conversation on the ticket. I have pushed a revision (3.0.2.2) with > documentation, perhaps you could review? In particular, I don't > adequately understand the :MIX option, s

Re: [asdf-devel] ASDF 3.0.2.1 released

Faré wrote: > Dear Robert, > > here are some code review comments on ASDF 3.0.2.1. Thank you very much for these comments. They are hugely helpful, and I will act on them. > > * Putting :asdf/find-system after :asdf in the recycle looks like it's > defeating the purpose; > you might as well rem

Re: [asdf-devel] ASDF 3.0.2.1 released

Dear Robert, here are some code review comments on ASDF 3.0.2.1. * Putting :asdf/find-system after :asdf in the recycle looks like it's defeating the purpose; you might as well remove it. * Maybe refactor duplicate-names so it doesn't inherit from system-definition-error ? Or have a function of

[asdf-devel] ASDF 3.0.2.1 released

ASDF 3.0.2.1 is the first candidate release for ASDF, containing several bug fixes. If you can, please grab this ASDF release and test it with your systems, and by running make test or make test-all Please report any bugs you find to the ASDF project on launchpad.net We'd like this to pave the

[asdf-devel] ASDF 3.0.2 released

With a great deal of patient instruction from Faré, I released ASDF 3.0.2 yesterday. It is far more stable, and provides a wider range of support, than its immediate predecessor. We encourage implementations to update their bundled versions of ASDF. Many thanks to Faré for years of hard work and

Re: [asdf-devel] ASDF 3.0.1

Faré wrote: > A future maintainer of ASDF may extend the > `(:version ,dependency ,minimum-version) > pattern for specifying dependencies with a > `(:version ,dependency ,minimum-version ,too-large-version) > pattern that allows to specify an exclusive upper bound on compatible > versions. > This

[asdf-devel] ASDF 3.0.1

Dear Lisp hackers, ASDF 3.0.0 was decidedly short-lived. Longer live ASDF 3.0.1! An undocumented feature of version-satisfies, since the early days of ASDF 1, was that it would reject a component that didn't exactly match the specified major version as well as otherwise be same or newer as specif

[asdf-devel] ASDF 3.0.0

Dear Lisp hackers, I'm proud to announce the release of release ASDF 3.0.0. Please test it and include it in your Common Lisp implementation or distribution. I'll have to produce some document explaining the innovations since ASDF 2.26, 2.000 and/or 1.369, but for now here are just the changes si

Re: [asdf-devel] ASDF-BUNDLE breaks ECL (and a rant about related stuff)

On Mon, May 13, 2013 at 3:17 PM, Faré wrote: > This regression was introduced somewhere in the 2.26.x rewrite, > and is hopefully fixed in asdf 2.33.10. Please test. > Thanks for the quick response: I will test it as soon as I return to Madrid. And sorry for the rant. I appreciate your work on m

Re: [asdf-devel] ASDF-BUNDLE breaks ECL (and a rant about related stuff)

Dear Juanjo, my apologies for breaking program-op on ECL for programs that didn't explicit depends-on asdf, asdf-driver or uiop, which used to work earlier, back when asdf-bundle's program-op used to be an ECL-only feature. This regression was introduced somewhere in the 2.26.x rewrite, and is ho

[asdf-devel] ASDF-BUNDLE breaks ECL (and a rant about related stuff)

Since 2.32 (probably earlier), ASDF can no longer produce standalone executables in ECL. The reason is that all those executables (stupidly in my opinion) have dependencies on libraries that should now be linked with the program. In particular, ASDF itself, UIOP, etc. Why is this so? Why do I hav

[asdf-devel] ASDF 2.33

Dear Lisp hackers, as things have settled down, ASDF is resuming a monthly release schedule. Therefore I am glad to announce ASDF 2.33. Please update your implementations, your distributions, etc., after suitable testing. Since previous release 2.32, it includes the following changes: * Portab

[asdf-devel] ASDF 2.32 released

Dear Lisp hackers, ASDF 2.32 was released in time for inclusion in the upcoming CCL 1.9. Once again, we invite all implementation vendors and distributors to upgrade the version of ASDF included in their releases. Yes, I know, that's a lot of releases in a bit more than a month. But it was also

Re: [asdf-devel] ASDF 2.30 released

On Thu, Feb 21, 2013 at 12:54 AM, Faré wrote: > We also invite all implementations to make the standard *readtable* > and *print-pprint-dispatch* tables immutable, > This is now the case in ECL. I will upload the fix tonight. -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28

  1   2   3   4   5   6   >