- asdf-devel - mailman3.common-lisp.net

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

[Asdf-devel] Request for hints debugging ASDF: SLIME-FIND-DEFINITION
by Robert P. Goldman 27 Nov '14

27 Nov '14

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 to edit -- that's like editing your binary). I have this function: (defun debug-asdf () (dolist (c (asdf::required-components :asdf/defsystem :keep-component 'asdf:cl-source-file)) (load (asdf:component-pathname c)))) and that does seem to load everything properly. However, use of SLIME-EDIT-DEFINITION after executing DEBUG-ASDF still dumps me into build/asdf.lisp instead of where I want to be. 2. SLIME-EDIT-DEFINITION on SBCL is confused by the WITH-UPGRADABILITY macro. Anyone know of a way to clue SLIME in to the fact that what's really wanted is the enclosed DEFUN* form, not the WITH-UPGRADABILITY macro? Interestingly, ACL is *not* fooled by this macro, and drops me where I want to be (although still in asdf.lisp instead of the component file). So this seems to be a problem with SB-INTROSPECT:FIND-DEFINITION-SOURCE, not SLIME per se. Cheers, r

2 2

[Asdf-devel] native-namestring in asdf/cache:normalize-namestring?
by Orivej Desh 25 Nov '14

25 Nov '14

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 the value of CFFI-GROVEL::EXE-FILENAME: Calling (cffi-grovel::exe-filename #p"grovel.cffi.lisp") returns #<pathname (with no namestring) :HOST #<sb-impl::unix-host {10002ACE43}> :DEVICE nil :DIRECTORY (:relative ".") :NAME "grovel.cffi" :TYPE nil :VERSION :newest> to ASDF/ACTION:COMPUTE-ACTION-STAMP which can't deal with it when called with :JUST-DONE NIL. Backtrace: http://report.quicklisp.org/cl-libssh2/2014-09-26/failtail.txt One solution is to make CFFI-GROVEL::EXE-FILENAME normalize resulting pathname: https://github.com/cffi/cffi/pull/52 Another is to make ASDF/CACHE:NORMALIZE-NAMESTRING call NATIVE-NAMESTRING instead of NAMESTRING. Who should be responsible for normalizing such a pathname, ASDF of CFFI-GROVEL?

3 3

[Asdf-devel] ASDF 3.1.4.1 (non-release) pushed
by Robert P. Goldman 21 Nov '14

21 Nov '14

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

1 0

[Asdf-devel] Mistakenly pushed mis-numbered version
by Robert P. Goldman 21 Nov '14

21 Nov '14

Please don't pull from the repo while I tidy this up, or there will be non-fast-forward merges. Sorry!

1 0

[Asdf-devel] Noticed CCL issue in Linux tests
by Robert P. Goldman 21 Nov '14

21 Nov '14

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 1.10. Unfortunately the transcript is not helpful (see attachment). Seems like I'm no longer able to parse all that quoting. Two questions: 1. Can anyone else replicate this? 2. Any reason we couldn't take the contents of that command line and stuff it into a lisp file to load? Thanks! R

1 0