asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] :here directive fails
by Kilian Sprotte 08 Apr '15

08 Apr '15

Hi, is (asdf:initialize-source-registry '(:source-registry (:directory (:here "asd")) :ignore-inherited-configuration)) still a valid call to make? I am getting the error NIL fell through ETYPECASE expression. Wanted one of ((EQL :USER-CACHE) (EQL :HERE) (EQL :HOME) (EQL :ROOT) CONS STRING PATHNAME). Running this through git bisect tells me that the last working commit is commit 61192882b468b74a7f5fbf810e138b94db5fdd2a Merge: f4a7eac 610ca23 Author: Robert P. Goldman <rpgoldman(a)gmail.com> Date: Tue Jan 8 13:16:34 2013 -0600 Merge branch 'master' of ssh://common-lisp.net/project/asdf/public_html/asdf The next commit then has a broken build and the next two commits fail with the above error, as does the current master. I will put a summary of those commits below. Regards Kilian FAILS commit 056f33a907f9ae3ffe5e0ae6aaa5f3b6f5bc863a Author: Francois-Rene Rideau <tunes(a)google.com> Date: Wed Jan 9 07:43:10 2013 -0500 2.26.64: checkpointing progress with define-package FAILS commit 4b1cea29891e45ee50c4114dd7b7c17b78cfc7fc Author: Francois-Rene Rideau <tunes(a)google.com> Date: Wed Jan 9 00:32:11 2013 -0500 2.26.63: more pathname hell. New pathname functions to work around more logical-pathname issues. See discussion with rpgoldman on asdf-devel, and see CCL ticket:953. Also, tweak build to reflect recent refactoring of asdf. WIP of define-package work needed for clean upgrade (still broken). broken commit 7c151aab3d9bf6460b7683c4498a230bf6ea9660 Author: Francois-Rene Rideau <tunes(a)google.com> Date: Tue Jan 8 15:34:51 2013 -0500 2.26.62: split into many packages, quick-build style. TODO: Create a define-package that can make it upgrade itself.

2 1

cl-launch 4.1.1.1
by Faré 01 Apr '15

01 Apr '15

(Only tangentially related to asdf; apologies if this is noise; please suggest a better channel.) I just pushed cl-launch 4.1.1.1, which minimally implements support for a --dispatched-entry feature that's mostly compatible with Xach's buildapp. Differences are: 1- like cl-launch in general, it works on all command-line Lisp implementations supported by ASDF, not just on SBCL and CCL 2- I don't do as much error checking as Xach; in case of conflict, last one wins. 3- I accept UIOP-style function designators for the main function, not just symbol designators, see uiop:ensure-function. Background: I'm more and more replacing my shell-scripts with CL scripts, but the startup time of a script can be very high if we load from fasl every time, even when no compilation is needed. On the other hand, dumping one image per script is expensive, with the smallest CL implementation (CLISP) taking about 16MB for every script. Therefore, I implemented --dispatched-entry in a way mostly compatible with buildapp. I can then dump a single image for all my scripts, and they start super fast, evaluate super fast, and only occupy a few tens of megabytes once. --dispatched-entry is implemented as a thin layer that delegates everything to a small new library call cl-launch-dispatch, to be distributed with cl-launch. That means it will actually slow things down a tiny bit if you use it without dumping an image, but won't slow things down at all if you don't use it and don't dump an image. Enjoy! —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Democracy is a religion too. It's the worship of jackals by jackasses. — H. L. Mencken

1 0

os-cond patch pushed and version bumped to 3.1.4.4
by Robert P. Goldman 30 Mar '15

30 Mar '15

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.

1 0

Bug in UIOP XDG implementation
by Jason Miller 29 Mar '15

29 Mar '15

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 Specification says that "If $XDG_CONFIG_DIRS is either not set or empty, a value equal to /etc/xdg should be used." 2) My understanding of uiop:user-configuration-directories is that it's listed in order of importance, but, from the XDG spec: "The base directory defined by $XDG_CONFIG_HOME is considered more important than any of the base directories defined by $XDG_CONFIG_DIRS" So, what I think is correct is that with $XDG_CONFIG_DIRS set it should return a list starting with $XDG_CONFIG_HOME, followed by the lists in $XDG_CONFIG_DIRS, and with it not set, should return a list of $XDG_CONFIG_HOME followed by /etc/xdg/common-lisp/ Even if that's not correct, due to #1 the current implementation is definitely wrong. Regards, Jason

4 6

Re: manual version
by Robert P. Goldman 24 Mar '15

24 Mar '15

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 a personal prefence - I dislike >> html manuals. I also tend to print such manuals out (I know, I know - >> very old school). Anyway, that makes it easy to get out of sync. >> >> What I am thinking is that it might be useful for the manual to >> contain an indication of the version of asdf that it pertains to. As, >> for example in the GNU Make manual, which has on the title page "GNU >> make Version 4.1". Perhaps an indication of this is already there in >> the manual, but I can't spot it. > > I'm not an expert on Texinfo, but I think we can figure out a way to have it get @value{VERSION} from the make scripts, and then we can put that in as a subtitle. > > I'll keep you posted. > OK, I have pushed a patch that will put the version numbers into the ASDF texinfo manual. The makefile for this uses a horrible snippet of perl, but I don't know a substitute. I am open to replacements. good night, all, r

2 1

How do I get the pathname of a CL-SOURCE-FILE
by Christian Schafmeister 23 Mar '15

23 Mar '15

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 objects? saw file: #<CL-SOURCE-FILE "cleavir-io" "packages" @0x113ac3518> saw file: #<CL-SOURCE-FILE "cleavir-io" "io" @0x113bacdd8> saw file: #<CL-SOURCE-FILE "cleavir-meter" "packages" @0x1152baf68> saw file: #<CL-SOURCE-FILE "cleavir-meter" "meter" @0x1153b4068> saw file: #<CL-SOURCE-FILE "cleavir-ast" "packages" @0x115d73ba8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "general-purpose-asts" @0x115f98b08> saw file: #<CL-SOURCE-FILE "cleavir-ast" "fixnum-related-asts" @0x115a1a978> saw file: #<CL-SOURCE-FILE "cleavir-ast" "float-related-asts" @0x11549ce78> saw file: #<CL-SOURCE-FILE "cleavir-ast" "cons-related-asts" @0x115027ab8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "standard-object-related-asts" @0x115196838> saw file: #<CL-SOURCE-FILE "cleavir-ast" "array-related-asts" @0x115303658> saw file: #<CL-SOURCE-FILE "cleavir-ast" "graphviz-drawing" @0x1153fdec8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "map-ast" @0x114073f68> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "packages" @0x113d2ffb8> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "clone" @0x113e0ec48> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "replace" @0x113ed67e8> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "hoist-load-time-value" @0x113f9bba8> saw file: #<CL-SOURCE-FILE "cleavir-primop" "packages" @0x1140c5c98> saw file: #<CL-SOURCE-FILE "cleavir-internationalization" "packages" @0x1144b0928> … Deleted another 100 entries ... Christian Schafmeister

3 2

How would I get a list of Common Lisp source files from a system
by Christian Schafmeister 22 Mar '15

22 Mar '15

Hi there, I’d like to get an ordered list of source files for a system that I would normally load with (asdf:load-system :cleavir) I need this because I’d like to compile the Cleavir source code (many interdependent systems) without having to compile and load ASDF. Then I could compile ASDF a lot faster and users would load it. Best, Christian Schafmeister Professor Chemistry Department Temple University

2 4

[Asdf-devel] :homepage :bug-tracker :mailto :long-name :source-control
by Faré 12 Mar '15

12 Mar '15

Shamed by a tweet by @hexstreamsoft, I made a very minimal attempt at documenting the existence since ASDF 2.27 of the :homepage :bug-tracker :mailto :long-name :source-control keywords to defsystem. I will leave for someone else to make real manual entries out of the information. NB: AFAIR, none of the types of these arguments is enforced by ASDF. Good luck! —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Efficiency is doing things right; effectiveness is doing the right things. — Peter Drucker

3 5

[Asdf-devel] Why won't accept relative pathnames in source-registry?
by Eitaro Fukamachi 19 Feb '15

19 Feb '15

Hi ASDF developers, I wanna ask a question about the specification of source-registry. ASDF doesn't allow relative pathnames in source-registry string intentionally. https://github.com/drmeister/asdf/blob/master/source-registry.lisp#L136 It seems the line has long history, however, why it won't accept relative pathnames? I think it would be useful when adding the current working directory to the source registry like: # doesn't work CL_SOURCE_REGISTRY=. sbcl --eval '(princ (asdf:system-source-directory :myapp))' Thanks, Eitaro Fukamachi

3 5

[Asdf-devel] Program with metaclass on MKCL.
by D. Martinez 05 Dec '14

05 Dec '14

Hello. Being new to "serious" CL programming I am hitting a brick wall right now in one CLOS project. After some time of infructuous searching I cannot find the source of my problem, which may be of either MKCL or ASDF but I lack the knowledge to debug this. Mr. JCB, who I have seen active on this list, may (hopefully!) be able to shed some light on the issue. The bug I encounter happens when I load the project by the means of ASDF. I can not reproduce it otherwise. It is triggered by a use of a custom metaclass, and it suggests that a file is loaded more times than it should. I have narrowed down the problem to a small program, so here it is: ;;;; hello.asd (asdf:defsystem #:hello :description "Describe hello here" :author "Your Name <your.name(a)example.com>" :license "Specify license here" :serial t :components ((:file "package") (:file "a")) :depends-on ()) ;;;; package.lisp (defpackage #:hello (:use #:cl)) ;;;; a.lisp (in-package #:hello) (defclass A-class (standard-class) ()) (defclass A (standard-object) () (:metaclass A-class)) * Case 1: load with MKCL only: mkcl -load package.lisp -load a.lisp OK, works as expected. * Case 2: compile with MKCL only and load: mkcl -load package.lisp -compile a.lisp OK, it produces a fas (shared library). I load it from REPL. It works. * Case 3: load or build with ASDF It fails (at the definition of class A). The error message is this: -> When redefining a class, the metaclass can not change.. It acts as if a.lisp was actually loaded twice. Same error as loading a twice in a row, as by this command. mkcl -load package.lisp -load a.lisp -load a.lisp My ASDF command: (asdf:operate 'asdf:load-op :hello) Same problem with compile-op and program-op. However, load-source-op does work without problem. (I always make sure to clear cache between asdf operations) I will happily provide more specific info at request. The bug occured on MKCL 1.1.9 and 1.1.10 git with bundled ASDF.

4 6

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel