Re: ASDF config file under Windows

The next step would be to add an ASDF plug-in so that ASDF can read its configuration from a CLAD set up…. :-) -- Robert P. Goldman On June 3, 2023 at 16:56:53, Marco Antoniotti (marco.antonio...@unimib.it(mailto:marco.antonio...@unimib.it)) wrote: > We. You need a CL to load A

Re: :initform vs. :default-initargs

be great. -- Robert P. Goldman On December 22, 2021 at 05:18:58, Attila Lendvai (att...@lendvai.name(mailto:att...@lendvai.name)) wrote: > dear list, > > i wanted to set the default-component-class of our own system subclass using > :default-initargs, but it's ignored beca

Re: Simple use of output-translations

You should be able to invoke the function initialize-output-translations on an s-expression like the one Stelian sent. -- Robert P. Goldman On October 22, 2021 at 16:35:07, Raymond Toy (toy.raym...@gmail.com(mailto:toy.raym...@gmail.com)) wrote: > Thanks. Is it possible to

Re: Upcoming bug fix release

Do you have an example of this failing you could share? And does this problem happen on earlier versions of ABCL? -- Robert P. Goldman On June 5, 2021 at 00:00:48, Mark Evenson (even...@panix.com(mailto:even...@panix.com)) wrote: > > > > On Jun 4, 2021, at 05:10, Robert Go

Re: "How-to" request

Oh, yes, you are right about :properties. I had forgotten. I generally add my own dedicated slot, but :properties is probably fine. -- Robert P. Goldman On March 20, 2021 at 09:23:21, Marco Antoniotti (marco.antonio...@unimib.it(mailto:marco.antonio...@unimib.it)) wrote: > Hi Rob

Re: "How-to" request

Neat! Thanks for posting the pointer! BTW, you might want to change the name from :properties to something like :doc-properties to avoid potential name collisions... -- Robert P. Goldman On March 20, 2021 at 09:11:45, Marco Antoniotti (marco.antonio...@unimib.it(mailto:marco.antonio

Re: "How-to" request

Yes, if you look at FIVEAM-ASDF, that is how John Maraist and I do it. We introduce a subclass of systems that has an extra slot holding the list of tests to be performed, and PERFORM reads that slot when doing TEST-OP. -- Robert P. Goldman On March 20, 2021 at 02:45:57, Marco Antoniotti

Re: Jenkins expertise?

Thanks for reaching out , Dave. I hadn't realized that cl.net had the full gitlab CI hooked up to it. Are there any resource issues? There are a lot of projects hosted there. That said, are there sufficient resources there if we start running a pipeline? -- Robert P. Goldman On October

Re: Lowercase naming requirement for systems?

Quick response for now: yes, lowercase naming is a requirement. There are a number of reasons for this, including the fact that CL's logical pathnames are case-insensitive. Best, R Sent from my iPhone > On Feb 17, 2019, at 01:21, Robert Dodier wrote: > > Hi, > > The ASDF manual says that

Re: why does ASDF ask to please only define system/test?

Thanks, Attila. I must say that as the remaining maintainer, this kind of complaining doesn't make me excited about doing my ASDF chores. This warning won't go away on my watch. Fare's change to support "slashy" systems is an elegant way to handle subsystems. I'm sorry that some people used

Re: Issues with Jenkins and clisp

Thanks for the information. I'll give it a try and report back. Best, R Sent from my iPhone > On Jul 28, 2018, at 15:39, Faré wrote: > > CLISP has long had semi-deterministic SIGSEGV issues like that: > reproducible, but going away at the slightest change in the test or > its invocation made

Re: ASDF recompile all files if ASD file is changed?!

Yes, this is a feature, not a bug. If you change the ASD file, ASDF has no way to know whether any compiled file in the system is up to date. For example, you could have added a system dependency that brings in a new use-package relationship and a macro, or reader macro that invalidated every

Re: "deprecated recursive use" warning

You're welcome, but really the intuition is due to Drew McDermott, I think in his ILC 2005 paper, which I recommend. (He describes a system like ASDF, but finer-grained, so that even individual data structures can be updated). This is key to understanding some of the ways ASDF is NOT like

Re: Testing for ASDF 3.3.2 and beyond?

Sorry. That was meant to be "master," not matter. Sent from my iPad > On Mar 17, 2018, at 09:36, Robert P. Goldman <rpgold...@sift.net> wrote: > > Just to be clear: this is matter, right? It's not one of the syntax control > branches? > > Sent from my iP

Re: Testing for ASDF 3.3.2 and beyond?

Just to be clear: this is matter, right? It's not one of the syntax control branches? Sent from my iPad > On Mar 17, 2018, at 07:51, Anton Vodonosov wrote: > > Results for these lisps: > > abcl-1.5.0-fasl43-linux-x86 > ccl-1.10-r16196-f96-linux-x86 >

Re: Testing for ASDF 3.3.2 and beyond?

dex.ru> wrote: > > Faré, hello. > > Sorry for replying so long - I'm almost paralyzed by too many things I need > to deal with currently. > I've started tests for the following commit. Will follow-up with the results. > > commit 2a5bc3bece8f97fdf64dc73a4e0544a55ae

Re: ASDF debugging on Hangouts?

That would be great. One question, would you please record the hangout and share it? (I have some work things that are making my schedule unpredictable for the next few weeks). I believe you can record hangouts to YouTube. Thanks Sent from my iPad > On Nov 28, 2017, at 12:32, Faré

Re: Possible incompleteness in INPUT-FILES for DEFINE-OP

Thanks. I'll add that. I just didn't want to duplicate code if there was already a method that did what I wanted Sent from my iPhone > On Jun 29, 2017, at 18:34, Faré wrote: > >> On Thu, Jun 29, 2017 at 7:28 PM, Robert Goldman wrote: >> What seems like

3.2.0

This is clearly my fault. I lost track of the plan. Going forward, I need to get a better handle on plans -- I've been to reactive, having discussions spread across launchpad, GitLab, IRC, and the mailing list. Here's one proposal: instead of reverting the recent merge, we could cut a release

Re: Misnamed secondary systems

I don't read fare's email as forbidding secondary systems, just those that are misnamed. So I don't think he's proposing to remove features, just check compliance with the naming convention. Maybe the proposal at hand is not described crisply enough. Sent from my iPad > On Nov 18, 2016, at

Re: Version 3.1.7.35 has been pushed

I think we wait for iolib, but probably not ASDF system connections. Its github site shows no commits for four years, so that might be a long wait Sent from my iPad > On Nov 16, 2016, at 23:49, Faré wrote: > > I sent these pull requests to fix the issues: >

Re: Another follow-up from yesterday's doc reviews

As I said, this is where the DWIM slipped in I never minded keeping track of packages, and in retrospect I claim that getting the package right imposes less complexity than trying to keep track of all the stuff ASDF does behind your back to keep you from having to type "ASDF:" Sent from my

Re: Another follow-up from yesterday's doc reviews

Actually now LOAD-ASD controls syntax, sets the readtable, controls the pretty-printer, sets up a cache, and a handler. And who knows what it will do tomorrow? For the record, I'm not a fan. I would prefer that asd files were normal lisp. But they aren't, so I don't think we should lie about

Re: UNSUPPORTED-FUNCTIONALITY Error [was Re: Version 3.1.7.7 has been pushed]

With all due respect, a few minutes ago you were saying I shouldn't expect to have the source code, in response to my desire to restore some of the source-finding functionality of load truename, but in this message you are telling me it's enough to have simple error objects because everybody

Re: UNSUPPORTED-FUNCTIONALITY Error [was Re: Version 3.1.7.7 has been pushed]

You are ignoring my proclaimed purpose of improving the testing of ASDF. Sent from my iPhone > On Aug 25, 2016, at 22:21, Faré wrote: > > I'd rather keep it simple. > > End-users don't care WHY something is failing, just THAT it is failing > gracefully and that the reason

Re: serious-condition

On 7/31/16 Jul 31 -9:06 PM, Faré wrote: >> The closest I'd be willing to go is to remove UIOP:*FATAL-CONDITIONS* >> > and replace it with a type definition for UIOP:FATAL-CONDITION. But >> > even that makes me feel bad. I guess we can keep this for now, but I'll >> > be a lot happier when it's

Re: serious-condition

On 7/31/16 Jul 31 -6:12 PM, Faré wrote: > On Fri, Jul 29, 2016 at 9:41 AM, Robert P. Goldman <rpgold...@sift.info> > wrote: >> On 7/28/16 Jul 28 -10:47 PM, Faré wrote: >>> On Thu, Jul 28, 2016 at 5:08 PM, Robert P. Goldman <rpgold...@sift.info> >>>

Re: serious-condition

On 7/28/16 Jul 28 -10:47 PM, Faré wrote: > On Thu, Jul 28, 2016 at 5:08 PM, Robert P. Goldman <rpgold...@sift.info> > wrote: >> Question: shouldn't I add this as >> >> (deftype FATAL-CONDITION ...) >> >> and try to use that everywhere, instead of writing

Request for advice on handling SERIOUS-CONDITIONs in ASDF tests

Previously, in the ASDF test suite, we would run tests, checking for errors, and if there were errors, we would exit with a non-zero status, signaling to our shell script that a test had failed. However, experimenting with ECL, I found that there were cases where ECL would fail with a

Re: How to fix arnesi:clean-op.

I'll look into this a bit. I'd be happy to see clean-op incorporated in ASDF. Note that budden's response about using touch is not necessary. To force a recompile one can simply use :force Sent from my iPhone > On May 8, 2016, at 09:50, TANIGUCHI Masaya wrote: > > I want

Re: Is it possible to load multiple versions of the same system?

Eran Gat, if I remember correctly, had an implementation of lexically scoped packages. That would provide the capability for having multiple versions of the same system live in one lisp image, but would require rewriting the systems in question and their consumers. TBH, this seems to me like a

Re: How does one declare non-lisp dependencies?

You could certainly create a class of ASDF component that would represent software packages/libraries like libfixposix. Then you would have the PERFORM methods on the objects of this class simply check for the presence of the library. You could have other ASDF components depend on objects of

Windows development will get easier

According to O'Reilly, Microsoft will be putting bash onto Windows 10. Given that, I propose we just wait this out instead of enjoying the full misery of translating our scripts to CMD.EXE... Yay! Sent from my iPhone

Re: ASDF status for 3.1.7 release

Unfortunately, the build went south for me at the first introduction of the precompilation into the build, so stable never happened for me. TBH, I would suggest the building happen outside the ASDF repository entirely. Scripting isn't part of the ASDF objective, so I think having a scripting

Re: ASDF status for 3.1.7 release

The last time I tried it, the build process had been changed to require a precompilation step for the script runner, and that precompilation step failed for me. Prior to that the lisp-based solution seemed to mostly work, but was not maintainable by me. ASDF is all I can handle; I need to have

ASDF 3.1.7 has been released

implementations. * Miscellaneous bug fixes. * Documentation improvements. * Restore original Makefile. -- Robert P. Goldman <rpgold...@sift.net> Wed, 23 Mar 2016 09:34:14 -0500

Re: test-sysdef-asdf failing

I'll fix it tomorrow, thanks for the explanation. I couldn't figure out how to salvage the old bump script, since there is a new one in the full lisp scripting system. Sent from my iPhone > On Feb 26, 2016, at 22:39, Faré wrote: > >> On Fri, Feb 26, 2016 at 1:45 PM,

Re: Time for 3.1.7 ?

I'll check the current version on Mac, Linux and Windows, as feasible. If I can, I will also add a couple of debugging functions to help people figure out when their configs go awry. We had correspondence that gave calls top make, but they are kind of complicated. Sent from my iPhone > On

ASDF 3.1.6 has been released

(ticket #1483948). * Fix misplaced fasl cache on Windows. * Miscellaneous bug fixes. * Documentation improvements. -- Robert P. Goldman <rpgold...@sift.net> Sat, 17 Oct 2015 15:01:34 -0500

Re: maintaining non-Lisp systems with ASDF

That's what :defsystem-depends-on is for. Please let me know if you don't find it adequately documented in the manual... Sent from my iPad > On Sep 24, 2015, at 19:41, Robert Dodier wrote: > >> On Wed, Sep 23, 2015 at 2:39 PM, Faré wrote: >> >>

Re: Tests failing on Allegro 10 preview, Mac OS X

Thanks. I'll look. On Aug 29, 2015, at 03:53, Faré fah...@gmail.com wrote: I've tried the Allegro 10.0 release candidate, and the script-support bizarrely fails to override the configuration when it passes an argument initialize-source-registry, that gets lost on its way to

Re: Almost there

I'm afraid I've forgotten: would you please send out the results URL(a)? Sent from my iPhone On Jul 12, 2015, at 20:34, Anton Vodonosov avodono...@yandex.ru wrote: 10.07.2015, 12:20, Anton Vodonosov avodono...@yandex.ru: 10.07.2015, 06:06, Faré fah...@gmail.com: Dear lispers, we're

Re: Release plan for asdf

Faré wrote: Dear Robert, I believe the plan to enable style-warnings for those using deprecated functions or missing useful metadata is great, but 1- justifies moving to version 3.2. 2- requires testing with a 3.2.0.x alpha release series that already have a version = 3.2, so no magic

Re: How would you feel...

Andreas Davour wrote: On Wed, 27 May 2015, Faré wrote: [snip] My SBCL is at 3.1.3. I think 3.1.4 is solid enough that it should be updated there. I've bugged SBCL hackers many time since last october, to no avail. But remember hwo it looks like from the outside, though. You are

Re: Metadata check [WAS Re: How would you feel...]

, r Regards Erik On May 27, 2015 8:54 PM, Robert P. Goldman rpgold...@sift.net mailto:rpgold...@sift.net wrote: Faré wrote: OTOH, it's probably A Bad Thing if you depend on a system for something you are doing, and don't know what license it uses. Well

Should we abandon support for IMAGE ops on Lispworks?

I'm starting to be inclined to suggest we abandon support for this kind of operation on Lispworks. Lispworks does not provide a portable means to invoke from the command-line, indeed invocation from the command line is *IMPOSSIBLE* unless you pay extra for a Professional license. Also,

Re: How would you feel...

Faré wrote: On Tue, May 26, 2015 at 2:55 PM, Robert P. Goldman rpgold...@sift.net wrote: Faré wrote: Oh well, I'm torn. I think it's a good thing, but maybe incompatible enough that we should release 3.1.5 now and start a 3.2.0 branch. I don't think this counts as incompatible, since it would

Metadata check [WAS Re: How would you feel...]

Faré wrote: OTOH, it's probably A Bad Thing if you depend on a system for something you are doing, and don't know what license it uses. Well, we haven't codified any format for :license. I suppose we could adopt the nomenclature used by Debian. Except what in Lisp circles goes by the name

Getting failure on LW 6 and 7 on Mac and Linux on test-run-program

Here's the error: TEST ABORTED: Undefined function LISP-INVOCATION/IMPLEMENTATIONS::INVOKE-LISP-VIA-SCRIPT called with arguments (:CROSS-COMPILE NIL :LOAD /Users/rpg/lisp/asdf/test/make-hello-world.lisp :EVAL (asdf-test::make-hello-image) :RUN-PROGRAM-ARGS (:INPUT NIL :IGNORE-ERROR-STATUS T

Re: Purpose of components of type :static-file?

Dave Cooper wrote: Hi, What is the intended purpose of the :static-files component-type in ASDF? I see a couple examples of their use in the ASDF manual, but didn't see an explanation or real example of how to use them downstream from including them in the defsystem form in the .asd file.

Re: Patch to UIOP/LISP-BUILD:GET-OPTIMIZATION-SETTINGS for SBCL

Douglas Katzman wrote: Hi ASDF developers, I'm changing SB-C::*POLICY* from a list to a struct. (This yields us a nice compile-file speedup.) Instead of accessing the global policy with (CDR (ASSOC ...)) it should be accessed with (SB-C::POLICY-QUALITY) as per the attached diff. This

EXPECTED test failures clisp

Do we have a way of indicating that we expect a test to fail? There's a string in the output that talks about Unexpected test failures in... but I am not sure if there's actually any notion of expected vs. unexpected test failure. IIRC in the past when I knew a test would fail I just used reader

Re: UIOP documentation?

Faré wrote: On Wed, May 6, 2015 at 1:11 AM, edgar edgar-...@web.de wrote: https://gitlab.common-lisp.net/asdf/asdf/blob/HEAD/uiop/README The correct link is: https://gitlab.common-lisp.net/asdf/asdf/blob/HEAD/uiop/README.md The only problem is that the .md at the end is missing. - edgar

Re: UIOP documentation?

Faré wrote: I looked at the link to the version that's supposed to have good docs: http://bimib.disco.unimib.it/people/Marco.Antoniotti/Projects/CL/HELAMBDAP/tests/asdf-uiop/docs/html/dictionary/dictionary.html AFAICT it shows only the docs for BACKWARD-INTERFACE, and maybe not even

Re: Ding dong the witch is dead!

Faré wrote: Dear lispers, with the recent release of LispWorks 7 (congratulations to the LispWorks team!), each and every maintained CL implementation now provides ASDF 3, and ASDF 2 can be declared officially dead. Adieu, ASDF 2, you served your purpose, but you won't be missed. I

Re: UIOP documentation?

Faré wrote: Robert, could you make website from master? And/or release. Many links are broken by the gitlab.common-lisp.net update. I just did that, and was able to follow the link to README.md for UIOP. Please LMK if you (or anyone else) has trouble getting at that file. Cheers, r

Re: UIOP documentation?

Faré wrote: UIOP has no manual, but it has a README.md which guides you through the code and links to a website with interactive help as extracted from docstrings. I included a direct link on the ASDF webpage in doc/index.html — but only the maintainer has the rights to update the actual

Re: New version of ASDF pushed

Faré wrote: In the launchpad bug at https://bugs.launchpad.net/asdf/+bug/1437480 you also mention: I believe that we should release this as 3.2 because of the incompatibility in the API with the new functions from UIOP. While I think we should indeed soon release 3.2, I believe that it

Re: New version of ASDF pushed

Faré wrote: Now, when I did a make bump, I got the following error message: Transforming file upgrade.lisp... done. Rebuilding ASDF with bumped version git commit -a -m Bump version to $(eval a=$(cat version.lisp-expr) ; echo $a) fatal: ..: '..' is outside repository [master 9120cf7]

Re: New version of ASDF pushed

Faré wrote: While I think we should indeed soon release 3.2, I believe that it is not so urgent that it can't wait for a few more useful changes, especially since we do provide backward compatibility functions for the old API. So I propose we release a 3.1.5 for now, and do a few more changes

New version of ASDF pushed

I have just pushed 3.1.4.5, which contains fixes to UIOP's configuration file finding/XDG functions needed to fix launchpad bug 1437480. Testing would be very much appreciated, especially by those using the configuration file finding functions.

Re: New version of ASDF pushed

Robert P. Goldman wrote: I have just pushed 3.1.4.5, which contains fixes to UIOP's configuration file finding/XDG functions needed to fix launchpad bug 1437480. Testing would be very much appreciated, especially by those using the configuration file finding functions. Sorry: typo

Re: default method for test-system?

Faré wrote: Dear ASDF users, what about this default method (or something similar) for test-op? (defmethod perform ((o test-op) (s system)) (loop :with name = (coerce-name s) :for suffix :in '( /test -test) :for test-system-name = (strcat name suffix) :for

Re: manual version

Mark Evenson wrote: On 3/24/15 03:12, Robert P. Goldman wrote: DJ wrote: How do I know whether the asdf manual I am looking at matches the version of asdf I have installed? Seems like we should encourage the implementations to make the manual available to their users. ABCL has [always

os-cond patch pushed and version bumped to 3.1.4.4

This patch passes all the tests for me that were passing before. I'm still not convinced that our patch for Bug 1437480 is ready to go yet, so I have held off that one, to minimize chances we'll need to backtrack.

Re: Bug in UIOP XDG implementation

Jason Miller wrote: Hi, With $XDG_CONFIG_DIRS unset, (uiop:user-configuration-directories) returns only $XDG_CONFIG_HOME/common-lisp/ However, with it set to /etc/xdg it returns a list that starts with /etc/xdg/common-lisp There are two problems with this: 1) The XDG Base Directory

Re: How do I get the pathname of a CL-SOURCE-FILE

Faré wrote: On Sat, Mar 21, 2015 at 11:27 PM, Christian Schafmeister chris.sc...@verizon.net wrote: I was given some code to extract all of the source files that a system requires for building. It gave me what you see below: How would I get the full pathname of one of these CL-SOURCE-FILE

Re: manual version

Robert P. Goldman wrote: DJ wrote: Thanks, Robert. I can find the latest manual, of course, on the asdf website. And I know that I am running asdf 3.1.3, which comes with ccl 1.10-r16196. (Clozure does not, as far as I can tell, supply a manual.) I always use the pdf version. Just

Re: manual version

DJ wrote: How do I know whether the asdf manual I am looking at matches the version of asdf I have installed? - DJ - I don't think we can help you with that problem. If your implementation supplies you a copy of ASDF, it should also supply a copy of the manual. There isn't really any way

Re: [Asdf-devel] :homepage :bug-tracker :mailto :long-name :source-control

Erik Huelsmann wrote: Hi Robert, On Sun, Mar 8, 2015 at 4:29 PM, Robert P. Goldman rpgold...@sift.net mailto:rpgold...@sift.net wrote: Interestingly, while we have the new metadata options listed in the grammar now, I see that the :version option is missing (although

Re: [Asdf-devel] :homepage :bug-tracker :mailto :long-name :source-control

Interestingly, while we have the new metadata options listed in the grammar now, I see that the :version option is missing (although documented in text). I'll fix that. cheers, r ___ Asdf-devel mailing list Asdf-devel@common-lisp.net

Re: [Asdf-devel] Why won't accept relative pathnames in source-registry?

Faré wrote: Isn't it allowed because it's never clear what directory they are relative to, considering that the user may have changed the getcwd() arbitrarily between startup and asdf parsing the source-registry configuration, which would cause interesting subtle bugs, that I wanted to avoid

Re: [Asdf-devel] Program with metaclass on MKCL.

D. Martinez wrote: I understand your hypothesis and I guess it makes sense. I have done the testing as you suggest. 1. load-source-op is good 2. load-op fails on the first time. But it produces fasl. 3. load-op succeeds, on the second time. In a larger program, the load-op seems to fail as

Re: [Asdf-devel] Request for hints debugging ASDF: SLIME-FIND-DEFINITION

Faré wrote: On Thu, Nov 27, 2014 at 12:30 PM, Robert P. Goldman rpgold...@sift.info wrote: Any advice about the attached would be helpful... 1. I thought I had figured out how to interactively get at the real definitions, instead of the ones dumped into build/asdf.lisp (which I don't want

Re: [Asdf-devel] native-namestring in asdf/cache:normalize-namestring?

Orivej Desh wrote: Currently, between CFFI-GROVEL and ASDF, neither normalizes pathnames with a dot in :NAME and NIL in :TYPE. (cffi-grovel:grovel-file grovel.cffi) in a system definition may cause an error under SBCL in ASDF/CACHE:NORMALIZE-NAMESTRING when it calls NAMESTRING on

[Asdf-devel] Noticed CCL issue in Linux tests

When testing the MKCL patch, I did a test-all on Linux, and found that CCL claimed not to build cleanly. But actually it wasn't failing to build cleanly: it was failing to correctly parse the second command line in test_clean_load. I am not seeing this on Mac, but there I have 1.9 instead of

[Asdf-devel] Mistakenly pushed mis-numbered version

Please don't pull from the repo while I tidy this up, or there will be non-fast-forward merges. Sorry! ___ 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.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

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 rpgold...@sift.info mailto:rpgold...@sift.info wrote: Jean-Claude Beaudoin wrote: On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman rpgold...@sift.info mailto:rpgold...@sift.info

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

Jean-Claude Beaudoin wrote: On Sun, Oct 5, 2014 at 11:03 PM, Faré fah...@gmail.com mailto:fah...@gmail.com 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

[Asdf-devel] New test-undeferred-warnings.script

I have put in a new test, test-undeferred-warnings.script, that illustrates your problem. It fails on the version of SBCL I have on my Mac, but succeeds on ACL and CCL. I think this is arguably an SBCL bug. I understand there's been some correspondence on the subject of deferring warnings on

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 readily

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 rpgold...@sift.info mailto:rpgold...@sift.info 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

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 rpgold...@sift.info 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

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 place. I see that test

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 (defun

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

to objects of its own creation. — Lew Mammel, Jr. On Wed, Oct 29, 2014 at 6:27 PM, Ilya Perminov ipermi...@dwavesys.com wrote: Robert P. Goldman rpgold...@sift.info writes: I cannot replicate this, but this may be a new behavior introduced by recent changes to SBCL, and I'm

Re: [Asdf-devel] resurrecting some tests

Dave Cooper wrote: For what it's worth, I experimented with my installed clisp (installed with homebrew on Mac, clisp 2.49). Just starting the plain clisp, and calling (ext:saveinitmem /tmp/try.image :executable t) results in an image which gives the same error: module 'syscall'

[Asdf-devel] Mac test update status

The following tests were run last night (update tests still running): abcl allegro8_64 allegro8_64_s allegro_64 allegro_64_s allegromodern8_64 allegromodern8_64_s allegromodern_64 allegromodern_64_s ccl clisp cmucl ecl lispworks sbcl Two test failures: 1. the clisp test-program failure that we

[Asdf-devel] clisp test failure

Here's what RUN-PROGRAM gets for arguments: (RUN-PROGRAM '(/Users/rpg/lisp/asdf/build/fasls/clisp-2.49-unix-x86_64/asdf/test/hello-world-example--all-systems.image -norc --quiet --quiet -ansi -I -on-error exit -x (uiop:restore-image :entry-point 'hello:entry-point :lisp-interaction nil))

[Asdf-devel] Status update on Linux tests

clisp 2.49: test-program fails We have had a great deal of correspondence about this. mkcl from git failing. We have agreed with JCB that this should not be a blocker, since the test failures seem to be related to mkcl issues. Mac tests will run overnight.

[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

[Asdf-devel] clisp on Linux [was Re: ASDF Release?]

Faré wrote: I get an all pass on Linux with my hand-compiled clisp. I have the clisp that you get with Linux Mint, and for me I get this failure: TEST ABORTED: These two expressions fail comparison with EQUAL: (NEST (LISP-INVOCATION:INVOKE-LISP :CROSS-COMPILE NIL :IMAGE-PATH

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

Jean-Claude Beaudoin wrote: On Sun, Oct 5, 2014 at 11:03 PM, Faré fah...@gmail.com mailto:fah...@gmail.com 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

Re: [Asdf-devel] Character encoding question in test-program

Faré wrote: On Sun, Oct 5, 2014 at 5:51 PM, Robert P. Goldman rpgold...@sift.info wrote: When I run this test, I get a style warning about the character encoding, because of Faré in the comment: Testing: test-program.script sbcl --noinform --no-userinit --no-sysinit --disable-debugger --eval

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

[Asdf-devel] Request for Lispworks test on Linux

It's time to do a new release, but I find that my Linux license for Lispworks has expired. LW kindly gives me a free license specifically for use to test ASDF, but it might take a little while to get it renewed. So if anyone out there has an LW license for Linux, and would be willing to test,

[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: (#compiled-closure 04039500 #compiled-debug-lexical-info 7fffcfee80d0) 1: (#compiled-function UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX

[Asdf-devel] Character encoding question in test-program

When I run this test, I get a style warning about the character encoding, because of Faré in the comment: Testing: test-program.script sbcl --noinform --no-userinit --no-sysinit --disable-debugger --eval

Re: [Asdf-devel] Request for Lispworks test on Linux

Faré wrote: On Sun, Oct 5, 2014 at 2:19 PM, Robert P. Goldman rpgold...@sift.info wrote: It's time to do a new release, but I find that my Linux license for Lispworks has expired. LW kindly gives me a free license specifically for use to test ASDF, but it might take a little while to get

  1   2   3   4   >