asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] Tests completed
by Robert P. Goldman 08 Apr '15

08 Apr '15

Over the weekend ran the full up tests, with upgrade as well as regression tests, on Mac OSX Lion with the following lispen: ccl clisp sbcl cmucl lispworks allegro_64 allegromodern_64 allegro8_64 allegromodern8_64 allegro_64_s allegromodern_64_s allegro8_64_s allegromodern8_64_s ecl abcl All tests completed successfully. I would like to do the following: 1. Add warnings as appropriate wrt changes in OPERATION hierarchy for code that extends OPERATION classes. 2. Add warnings for people using ABCL or ECL + bundle-op on Mac OS. ...and then do a release. Cheers, r

4 21

[asdf-devel] clisp, logical pathnames, and ASDF
by Robert P. Goldman 08 Apr '15

08 Apr '15

I have been grappling with my inability to upgrade clisp, and find myself confused by the following events in my transcript: [17]> (uiop/pathname:ensure-pathname "home:lisp;asdf;") #P"home:lisp;asdf;" [18]> (probe-file (merge-pathnames (uiop/pathname:ensure-pathname "home:lisp;asdf;") "asdf.asd")) NIL [19]> (translate-logical-pathname "home:lisp;asdf;asdf.asd") #P"/Users/rpg/lisp/asdf/asdf.asd" [20]> (probe-file (translate-logical-pathname "home:lisp;asdf;asdf.asd")) #P"/Users/rpg/lisp/asdf/asdf.asd" [21]> (probe-file (merge-pathnames (translate-logical-pathname "home:lisp;asdf;") "asdf.asd")) #P"/Users/rpg/lisp/asdf/asdf.asd" Am I for some reasonnot to expect that the standard pathname functions (e.g., merge-pathnames) will work with logical pathnames? The online clisp manual page discussing LOGICAL PATHNAMES says only: "No notes." http://www.clisp.org/impnotes/log-path.html But as I understand the CLHS on MERGE-PATHNAMES, with reference to the definition of "pathname designator", the above behavior seems to be non-conforming. I am not at all experienced with clisp, and find myself on strange and shaky ground here. thanks, r

3 7

[asdf-devel] Ordering of system :depends-on elements
by Zach Beane 08 Apr '15

08 Apr '15

A few projects in quicklisp work something like this: ;;; foo.asd (defsystem foo ...) (defsystem foo-extra ...) ;;; bar.asd (defsystem bar :depends-on (:foo-extra :foo)) With asdf 2, (asdf:load-system "bar") seems to work fine, I guess because asdf 2 does the equivalent of find-system on the elements from right-to-left. With asdf 3, it doesn't seem to work fine, I guess because asdf 3 does the equivalent of find-system on the elements from left-to-right. Are those guesses correct? What's the best way to have a system definition that works equally well in asdf2 and asdf3 in this kind of situation? Zach

7 15

[asdf-devel] is there a built in way to prevent ASDF from trying to upgrade itself?
by Gary King 08 Apr '15

08 Apr '15

thanks, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

[asdf-devel] Test status for ASDF
by Robert P. Goldman 08 Apr '15

08 Apr '15

Running on 64-bit Mac: lispworks fails test-module-pathnames (sometimes) clisp all pass sbcl all pass ecl test-bundle fails. I think this is an ECL bug, or a bug in the MacPorts packaging. cmucl all pass abcl test-bundle fails. This is a different problem from the ECL bug. It's https://bugs.launchpad.net/asdf/+bug/1207073 On 64-bit Linux: ccl sbcl cmucl allegro allegromodern lispworks all pass. But I have seen test-module-pathnames fail here on lispworks -- there seems to be an odd interaction between the test and make that is causing this to go wrong. Haven't had time to track down this intermittent failure.

2 1

[asdf-devel] defsystem :version (:read-file-line ...) fails because :at key isn't recognized
by Vsevolod Dyomkin 08 Apr '15

08 Apr '15

Hi, Basically, the problem is described in the message header. Whereas :read-file-form option is used by ASDF itself, :read-file-line isn't used and wasn't tested. Attached is a patch with relevant test cases and fixes. I would also suggest refactoring the code, because the code paths for :read-file-form and :read-file-line are almost identical, but are implemented in separate functions. Best regards, Vsevolod Dyomkin +38-096-111-41-56 skype, twitter: vseloved

4 5

[asdf-devel] quick-build support for ASDF
by Faré 08 Apr '15

08 Apr '15

I implemented support for quick-build in ASDF. Please review before it gets merged into the master branch. https://bugs.launchpad.net/asdf/+bug/1230368 http://common-lisp.net/gitweb?p=projects/asdf/asdf.git;a=shortlog;h=refs/he… Note that until an ASDF recent enough to include this support is widely available, you may have to use asdf-package-system, which is basically the same thing packaged as an add-on: git://common-lisp.net/projects/asdf/asdf-package-system.git http://common-lisp.net/gitweb?p=projects/asdf/asdf-package-system.git For backward compatibility with older versions of ASDF, I recommend the following: (defsystem top-of-my-quick-build-style-hierarchy :class package-system :defsystem-depends-on #.(unless (find-class 'package-system nil) '(:asdf-package-system))) —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org It's better to know nothing that to know what ain't so. — Josh Billings

1 0

[asdf-devel] ASDF 3.0.0
by Faré 08 Apr '15

08 Apr '15

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 since 2.33. As you can see, it's very minor stuff, and ASDF has been mostly stable these last two months, which is a good sign and the reason why I'm making an official 3.0.0 release. I'm also inserting a new digit in the version, so releases will have three digits: 3.0.0, 3.0.1, etc. will be minor continuations of 3.0. 3.1.0 will be the next "major" milestone in a series that preserves backward compatibility, and 4.0 (if ever) will be the next major release that doesn't. But I probably won't be there to see it, because I'm moving away from my Common Lisp job in Cambridge MA to some new as yet undetermined opportunities in NYC that are unlikely to see me do Common Lisp for a living, and I plan to try out different Lisps for a hobby (Racket, Maru, etc.). * Portability: have *uninteresting-conditions* be empty by default. Move stuff to *usual-uninteresting-conditions*, unused by default. Will make the SBCL team happy. Also, fix tests on ABCL. Fix regression of program-op on ECL, by implicitly linking in UIOP or ASDF. * UIOP: improvements to slurp-input-stream and thus run-program, notably accepting T as alias for *standard-output*, for better backward-compatibility of the deprecated run-shell-command. New macro with-output-file. * POIU support enhanced with various tweaks. * Build cleanup so make and concatenate-source-op create the same asdf.lisp —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The sunlights differ, but there is only one darkness. — Ursula K. LeGuin, "The Dispossessed" There are 40 kinds of lunacy, but only one kind of common sense. — African proverb

2 2

[asdf-devel] Re: Help with cl-launch
by Luís Oliveira 08 Apr '15

08 Apr '15

[Cc-ing asdf-devel] On Tue, Jan 14, 2014 at 1:14 AM, Faré <fahree(a)gmail.com> wrote: > Wow. If asdf 3.0.3 loads 2.14, that's a notable bug indeed. I have a faint > how that the bug is somehow in something other than asdf itself. Can you > confirm and give steps to reproduce? Ubuntu 13.04 apt-get installed cl-asdf (2:2.24-1) Grabbed the 2014-01 CMUCL snapshot luis@fusubu:~$ cmucl -noinit CMU Common Lisp snapshot-2014-01 (20E Unicode), running on fusubu With core: /home/luis/cmucl/lib/cmucl/lib/lisp-sse2.core Dumped on: Sat, 2014-01-04 19:49:03Z on lorien2 See <http://www.cmucl.org/> for support information. Loaded subsystems: Unicode 1.29 with Unicode version 6.2.0 Python 1.1, target Intel x86/sse2 CLOS based on Gerd's PCL 2010/03/19 15:19:03 * (require :asdf) ; Loading #P"/home/luis/cmucl/lib/cmucl/lib/contrib/asdf/asdf.sse2f". ("ASDF") * (asdf:load-system 'whatever) Warning: You are using ASDF version 3.0.3 (probably from (require "asdf") or loaded by quicklisp) and have an older version of ASDF (and older than 2.27 at that) registered at #P"/usr/share/common-lisp/source/cl-asdf/asdf.asd". Having an ASDF installed and registered is the normal way of configuring ASDF to upgrade itself, and having an old version registered is a configuration error. ASDF will ignore this configured system rather than downgrade itself. In the future, you may want to either: (a) upgrade this configured ASDF to a newer version, (b) install a newer ASDF and register it in front of the former in your configuration, or (c) uninstall or unregister this and any other old version of ASDF from your configuration. Note that the older ASDF might be registered implicitly through configuration inherited from your system installation, in which case you might have to specify :ignore-inherited-configuration in your in your ~/.config/common-lisp/source-registry.conf or other source-registry configuration file, environment variable or lisp parameter. Indeed, a likely offender is an obsolete version of the cl-asdf debian or ubuntu package, that you might want to upgrade (if a recent enough version is available) or else remove altogether (since most implementations ship with a recent asdf); if you lack the system administration rights to upgrade or remove this package, then you might indeed want to either install and register a more recent version, or use :ignore-inherited-configuration to avoid registering the old one. Please consult ASDF documentation and/or experts. ; Loading #P"/usr/share/common-lisp/source/cl-asdf/asdf.asd". ; Loading #P"/usr/share/common-lisp/source/cl-asdf/asdf.lisp". Exporting these symbols from the ASDF package: (FIND-SYMBOL*) results in name conflicts with these packages: ASDF/USER [Condition of type LISP::SIMPLE-PACKAGE-ERROR] Restarts: 0: [UNINTERN-CONFLICTING-SYMBOLS] Unintern conflicting symbols. 1: [SKIP-EXPORTING-THESE-SYMBOLS] Skip exporting conflicting symbols. 2: [CONTINUE ] Return NIL from load of #P"/usr/share/common-lisp/source/cl-asdf/asdf.lisp". 3: [RETRY ] Retry compiling #<CL-SOURCE-FILE "asdf" "asdf">. 4: [ACCEPT ] Continue, treating compiling #<CL-SOURCE-FILE "asdf" "asdf"> as having been successful. 5: [ABORT ] Return to Top-Level. Debug (type H for help) (EXPORT FIND-SYMBOL* #<The ASDF package, 39/64 internal, 25/194 external>) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:code/package.lisp. 0] This seems to be a bug with ASDF 3.0.3 as I can reproduce the same issue with SBCL 1.1.14 if I load ASDF 3.0.3 but /not/ when I use the bundled ASDF 3.0.2. HTH, -- Luís Oliveira http://kerno.org/~luis/

2 1

[asdf-devel] Buggy release
by Stelian Ionescu 08 Apr '15

08 Apr '15

The last commit causes this: ; caught ERROR: ; READ error during COMPILE-FILE: ; ; The function ASDF::FIND-SYMBOL* is undefined. ; ; (in form starting at line: 3452, column: 53, file-position: 150201) -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

4 10

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel