asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

Release 3.1.6
by Robert Goldman 22 Sep '15

22 Sep '15

Kevin, Does head currently work for you with the new Allegro (and with 9.0) on all three platforms? If so, I'm inclined to suggest we bless this as 3.1.6, since I know of no regressions on other implementations. Out of a sense of tidiness, I'd be happier if you had an x.y.z release version in your released ACL, instead of some transient internal version. But I'm going to be quite busy for the remainder of the month, so if you could let me know ASAP, I will try to squeeze the release around other activities in time that you can incorporate it in ACL. For you, ideally, it should just be a matter of getting a version with a tidier release number. Cheers, Robert

1 0

Standalone application delivery
by Faré 17 Sep '15

17 Sep '15

Dear Lispers, is any of you interested in automating application delivery using ASDF? Now that I fixed ASDF's bundle operations and CFFI, the missing piece is the part where the bundled object files are linked against the runtime to produce a self-contained executable. Is anyone interested in writing it? I have all the pieces (at least for SBCL), but assembling them is not my top priority at the moment. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org It's not ignorance that does so much damage; it's knowing so darned much that ain't so. — Josh Billings

2 4

ASDF 3.1.5 test suite issues on ACL (8.2 and 10.0 GM)
by Kevin Layer 17 Sep '15

17 Sep '15

Hi, all. I had an spr with Faré, but I figure it's better to have this discussion on asdf-devel. First, as Faré pointed out, ACL was releasing non-release versions of ASDF. I've rectified that, and I will be using the `release' branch from now on. Second, I can't build 3.1.5 on Windows. See below. Third, I would really love to include the ASDF tests as part of the ACL test suite. It would have prevented so many headaches. To that end, I see these problems: 1. There are reported errors, even on ACL 8.2. I can send the details, but I'm sure someone else can reproduce this. I used ALLEGRO=.../alisp make t u l=allegro in a clone of the asdf repo on the release branch. I used an 8.2 alisp, which was not in my PATH, btw. I don't have any lisps in my PATH (because I want to explicitly choose the version when I run it). 2. The symbolic link issue. The test suite doesn't run at all when the source files are available via a symbolic links. I'll be happy to get some workaround (a file loaded before the tests start so I can set *resolve-symlinks* to nil?). As for the Windows build problem: ;;; Compiling file sys:;contrib;asdf.lisp ;;; (C:\src\scm\acl82.32\src\cl\src\contrib\asdf.lisp) ; While compiling (:top-level-form "asdf.lisp" 321294): Error (from error): Invalid pathname #P"cache": Expected an absolute pathname Once I can build a release version of ASDF, I'll put it out as a patch on 8.2, 9.0 and 10.0. Once the testing issues are resolved, I will immediately add it to the test suite. Thanks. Kevin

6 28

Testing Allegro 10 GM on Windows
by Robert Goldman 16 Sep '15

16 Sep '15

I have just run the tests of HEAD on Windows with the GM. HEAD passes all the tests. Or almost.... I get failures on "allegro" and on "sbcl". I'm pretty sure that these are both bogus, because sbcl wasn't even an element of ASDF_TEST_LISPS! And I did a "make clean" before running the tests. So I suspect something oddball is going on. Don't have time to do any more checking now, though. cheers

1 0

Tests failing on Allegro 10 preview, Mac OS X
by Robert Goldman 11 Sep '15

11 Sep '15

The test-configuration.script and test-logical-pathname.script are failing on the latest Allegro 10 preview on Mac OS X on all the Allegro modern variants, and on the ANSI SMP variants. All tests pass on alisp non-SMP and alisp8 non-SMP. Test configuration: Running test-configuration.script with acl-10.0.pre-final.30s-macosx-x64 ; Loading /Users/rpg/lisp/asdf/test/test-configuration.script subdirectories of dir2/: (#P"/Users/rpg/lisp/asdf/build/dir2/dir3/" #P"/Users/rpg/lisp/asdf/build/dir2/dir4/") subdirectories of dir5/: (#P"/Users/rpg/lisp/asdf/build/dir5/dir6/" #P"/Users/rpg/lisp/asdf/build/dir5/dir7/") Source Registry: #<EQUAL hash-table with 22 entries @ #x1000cb1762> TEST ABORTED: the assertion (FIND-SYSTEM :FOO0 NIL) failed. test-logical-pathname: Test logical pathnames in source-registry, non-recursive TEST ABORTED: Component :TEST-LOGICAL-PATHNAME not found Is this the known no-trailing slash problem? Cheers, r

4 11

Pushed some docstrings
by Robert Goldman 08 Sep '15

08 Sep '15

I pushed documentation strings for some of the bundle operations. Open for comments about their accuracy, helpfulness, etc. At some point I would also like to reopen the issue of how to sync up docstrings and manual. The SBCL manual seems to have a solution to this problem. I'd be willing to use something like Didier's decIt, too. But I need a solution that wouldn't destroy the existing manual. Prefer TeXinfo, also. No Markdown need apply! ;-)

1 0

ECL test failures
by Robert Goldman 31 Aug '15

31 Aug '15

I just ticketed four new ASDF test failures on Mac with the ECL 16.0.0 version that I got from Daniel Kochmanski.... Looks to me like there may be some unhappiness with Apple's compiler, and there may be some issues with temporary file handling. https://bugs.launchpad.net/asdf/+bug/1490585 https://bugs.launchpad.net/asdf/+bug/1490587 https://bugs.launchpad.net/asdf/+bug/1490588 https://bugs.launchpad.net/asdf/+bug/1490589 Also on Mac OS X I am getting many warnings that look like this: /Users/rpg/lisp/asdf/build/fasls/ecl-16.0.0-unknown-macosx-x64/asdf/build/asdf.c:11316:1: warning: control reaches end of non-void function [-Wreturn-type] I'd love to have these resolved before making a 3.1.6... Cheers, r

2 3

lisp-invocation with lispworks very unpleasant
by Robert Goldman 31 Aug '15

31 Aug '15

On my Mac, when I run the tests on Lispworks, it insists on opening a new terminal window for every LW job, each of which has something like this in it: rpg@rpgoldman: ~ $ /var/tmp/lwtemp_rpgoldman_72030319WbgIm.command ; exit; These windows *must be closed by hand*, which makes testing lispworks unbearable. Anyone have any idea why this happens? thanks, r

1 0

Toward an ASDF 3.1.6 ?
by Faré 31 Aug '15

31 Aug '15

Dear Robert, I know you wanted to proceed to making new developments in an ASDF 3.2, but I believe the bad default cache computation on Windows makes it a good idea to release an ASDF 3.1.6 sometime soon. Bonus will be some concurrency fix and a better run-program on ECL. I still advocate merging in the minimakefile branch before 3.1.6. It will really make releasing and testing easier, especially on Windows. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org You may easily play a joke on a man who likes to argue — agree with him. — Edgar Waston Howe

2 2

Package inferred system base pathname
by David Vázquez 30 Aug '15

30 Aug '15

Hi, In the past I have used modules with the pathname keyword in order to specify that a group of files come from a subdirectory. However, I cannot find how to do this if I use the package inferred system approach. Basically what I would like to achieve is: (asdf:defsystem :myproject :name "" :description "" :version "0.0.1" :pathname "src" ;; non-existing keyword :class :package-inferred-system :defsystem-depends-on (:asdf-package-system) :depends-on (:myproject/all)) and all.lisp will be loaded from src/all.lisp. Is that possible somehow? Thanks in advance. David.

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel