asdf-devel

asdf-devel@common-lisp.net

2 participants
1378 discussions

[Asdf-devel] Character encoding question in test-program
by Robert P. Goldman 06 Oct '14

06 Oct '14

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 "'(#.(load(string'|script-support.lisp|))#.(asdf-test::load-asdf)#.(asdf-test::frob-packages)#.(asdf-test:run-test-script'|test-program.script|))" STYLE-WARNING: Character decoding error in a ;-comment at position 1 reading source stream #<FD-STREAM for "file /Users/rpg/lisp/asdf/uiop/contrib/debug.lisp" {10043F6093}>, resyncing. should lisp-invocation somehow be requesting UTF-8? R

2 2

[Asdf-devel] Fwd: ASDF test failure on MKCL linux
by Jean-Claude Beaudoin 06 Oct '14

06 Oct '14

---------- Forwarded message ---------- From: Jean-Claude Beaudoin <jean.claude.beaudoin(a)gmail.com> Date: Mon, Oct 6, 2014 at 7:30 PM Subject: Re: [Asdf-devel] ASDF test failure on MKCL linux To: "rpgoldman(a)sift.net" <rpgoldman(a)sift.net> On Mon, Oct 6, 2014 at 5:38 PM, Robert Goldman <rpgoldman(a)sift.net> wrote: > After disabling test-try-refinding, I get two more test failures on MKCL: > > ... > The former looks like some disagreement between ASDF and MKCL about what > extended MKCL system initialization arguments are permitted. Is it also > an MKCL bug, or is it our fault? If it's our fault, so be it. > Otherwise, I believe that instead of turning some tests on and off on > MKCL (and potentially forgetting to re-enable them), I would rather > simply drop MKCL testing until such time as these bugs are fixed. > > Thoughts? > > Nothing jumps at me from what you are describing here. So as a matter of principle I will approach this second report as separate problem until it can be clearly established otherwise. I guess I will have to simply go through the ASDF test suite on my own and work each problem in turn until they all get resolved. That's on my list of things to do in the coming hours. Until I get back to you with the fixes it is probably not very useful for you to keep on testing on MKCL. But, in any case, be assured that I value your bug reports very highly. Thanks, Jean-Claude

1 0

[Asdf-devel] ASDF test-program failure, clisp Mac OS X
by Robert P. Goldman 06 Oct '14

06 Oct '14

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 :IMAGE-PATH (NATIVE-NAMESTRING IMG) :EVAL "(uiop:restore-image :entry-point 'hello:entry-point :lisp-interaction nil)" :RUN-PROGRAM-ARGS '(:OUTPUT :LINES :ERROR-OUTPUT T))) evaluates to ("[4]> hello, world") '("hello, world") evaluates to ("hello, world") Best, r

2 1

[Asdf-devel] Request for Lispworks test on Linux
by Robert P. Goldman 05 Oct '14

05 Oct '14

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, that would be great. If you qualify, but don't know how to run the tests, just drop me a line and I'll send you instructions. Many thanks! Robert

2 2

[Asdf-devel] ASDF Release?
by Faré 05 Oct '14

05 Oct '14

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 soon time for a 3.1.4 release. Anton, can you run a full grid test with ASDF 3.1.3.10? Robert, do you agree that the code is ripe for release? NB: all enhancements from the minimakefile branch have been merged into master, except for the Makefile itself and the replacement of asdf-builder and run-tests.sh by the lisp script asdf-tools. So it's possible to merge that branch into master without any change to asdf.lisp itself, or its test suite and other associated scripts. Only the test and release infrastructure will be upgraded. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Don't worry about results. You can't wish them into existence. Focus on the process. You have decision power on it. And it will take care of results.

2 1

[Asdf-devel] uiop/os:setenv?
by Mirko Vukovic 04 Oct '14

04 Oct '14

Hi, Does uiop/os have a function for setting environment variables? I have not found any in ASDF 3.1 Thanks, Mirko

2 1

[Asdf-devel] Semantics of asdf:system-relative-pathname
by Ralf Mattes 04 Sep '14

04 Sep '14

Hello list, I just stumbled overthe following strangeness [1]: I've some code in directory foo that contains two asdf files, foo.asd and foo-test.asd, the later contains the following definition: (defsystem "foo-test" :version "0.1" :pathname "t" :serial t ..... ) Now, if I evaluate (asdf:system-relative-pathname :foo-test "baz" :type "rsc") I get a pathname relative to the _asdf-file_, while evaluating: (merge-pathnames "baz.rsc" (slot-value (asdf:find-system :foo-test) 'asdf::absolute-pathname)) yields the correct/expected pathname (i.e. one that honors the pathname spec. of the asdf system). Is this really intended behavior or just an oversight? Cheers, Ralf Mattes Footnotes: [1] in the sense of not following the principle o fleast astonishment

3 4

Re: [Asdf-devel] startup times and initialize-source-registry
by Ben Hyde 02 Sep '14

02 Sep '14

Would changing (:tree <path>) so it accepts an optional argument be less adhoc? Possibly (:tree <path> &key (depth nil) (don-not-recure-after-asdf-encountered nil)) That said this would have little if any value in my use case. I point ask it to sweep over my the directory where all my coding lives, and most of the directories in there are not lisp, and so there ain’t any asd files in those. - ben

4 15

[Asdf-devel] Minor minimakefile nit
by Robert P. Goldman 02 Sep '14

02 Sep '14

The minimakefile help lists: archive alias for command make-and-publish-archive but make-and-publish-archive is not listed as a command in the help, nor in the makefile. Is this description out of date? Question: can we do a long help for individual commands, like make help archive? As an aside, I would say that if one is interested in making CL a serious scripting contender, some equivalent of perl's Getopt::Long library for command line parsing (perhaps Didier's Clon would fit the bill?), and pod inline documentation is going to be critical. I pushed a comment on the makefile to explain at the top how to get help. Cheers, r

3 2

[Asdf-devel] Problem with Minimakefile branch -- was Re: Merging experimental-submodules
by Robert P. Goldman 02 Sep '14

02 Sep '14

Kambiz Darabi wrote: > I don't know how many people are devs and how many people just 'users' > in the sense that they clone the repo and use it without caring about > the dependencies of asdf. > > But your point is definitively valid. Actually, Kambiz's point is a good one, and it illustrates a real problem with the minimakefile branch. With the old makefile, all someone needed to do if they were to checkout and test ASDF was to grab the git repo, and type make test l=<my lisp> Now this process is substantially more complicated because now the user will have to go to substantially more work to get our not extensively tested CL infrastructure up and running. We should seriously consider revising the minimakefile so that testing does not require CL scripting, but instead goes back to using make and bash alone. Best, r

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel