asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

[asdf-devel] Results of an automated study of ASDF practices
by Juan Jose Garcia-Ripoll 13 Apr '10

13 Apr '10

... with my usual trolling http://groups.google.com/group/comp.lang.lisp/msg/4fc15114d6865348 FYI -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

1 0

[asdf-devel] How can I muffle ASDF2 chatter in one shot?
by Jean-Claude Beaudoin 13 Apr '10

13 Apr '10

Hello all, In ASDF2 (I am still using 1.661) is it possible turn off all "informational" output in one single operation? Looking at the source I see that there is a bunch of :verbose arguments to most (all?) of ASDF main entry points, but each of these have hard coded default values of T. This way one has to pass a ":verbose NIL" pair on each call to ASDF in order to get silence. Couldn't we have a *asdf-verbose* global that would give the default value of those :verbose arguments? Then a single (setq *asdf-verbose* nil) would allow the whole thing to go in "run silent, run deep" mode. Thanks Jean-Claude Beaudoin

2 1

[asdf-devel] ASDF 1.671: feature complete - please test!
by Faré 13 Apr '10

13 Apr '10

Dear all, with ASDF 1.671, I've updated the website and hopefully fixed all the bugs due for ASDF release 2. Could you be so kind as to severely test it on your platform of choice and report bugs? I would also invite implementers and system distributers to test-drive it. If you have a beta branch, I would even invite you to include the new ASDF in your beta branch, assuming it passes your preliminary tests. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Reevaluate your ends periodically — if some of them or in contradiction with reality or with each other, abandon or amend them without mercy — and those you keep, pursue without any apology.

4 5

[asdf-devel] new asdf does not like matlisp.asd
by m_mommer＠yahoo.com 11 Apr '10

11 Apr '10

Hi, what follows is, as far as I am concerned, an observation, and not a bug report. Maybe it is an interesting issue to keep in mind. So I upgraded to the new asdf, and observed the following. When I load matlisp with the .asd attached, I get an error that goes like this /usr/bin/ld: cannot open output file /home/mommer/.cache/common-lisp/sbcl-1.0.37-linux-x86-64/home/mommer/dev/matlisp/lib/libmatlisp.so: No such file or directory collect2: ld returned 1 exit status The reason for the ld error is that that ^.*/lib/.* does not exist, and again the reason seems to be this: (slightly edited) -------------- [...] (defsystem :matlisp :components ((:unix-dso "alien code" :pathname "" :dso-name "lib/libmatlisp" ;; barf :components ((:alien-module "BLAS" :pathname "LAPACK/BLAS/SRC/" [...] ---------------- I presume one can defend the new asdf here, and I can fix it for me by removing the "lib/" as it does not matter one iota. But I also would expect this to come up again. Regards, Mario.

5 27

[asdf-devel] Upgrade to ASDF 2 with ASDF-BINARY-LOCATIONS
by Robert Goldman 11 Apr '10

11 Apr '10

If one was to start up a lisp with asdf and asdf-binary-locations loaded, and then installed asdf2? Is this expected to run at all well? Would it be reasonable to trap this case and either refuse to run, or somehow undo asdf-binary-locations? I'd like to be able to do some more ASDF2 testing, but if ASDF2 can't be installed over ASDF 1 + A-B-L, that makes it more difficult... Thanks, r

2 1

[asdf-devel] :logical-hostname
by Juan Jose Garcia-Ripoll 10 Apr '10

10 Apr '10

One of the common problems that ASDF users faced when introducing the new binary location system is finding out where things reside. Another problem we will eventually find is locating the resources associated to an ASDF system which has been replaced by a precompiled version. In general it would be desirable for a system to be able to locate its resources (additional files, icons, bitmaps, etc) using logical pathnames. For that purpose I have coded a small patch that adds a new keyword, :logical-host, to DEFSYSTEM. The keyword defines a logical pathname translation from "**;*.*.*" to "path/to/asdf/or/pathname/argument/**/*.*" This way we may have (defsystem :cl-unicode :logical-host "cl-unicode" ...) and in the sources load the databases such as "cl-unicode:uppercase-table.dat" https://bugs.launchpad.net/asdf/+bug/551222 -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

4 33

Re: [asdf-devel] new asdf does not like matlisp.asd
by Robert Goldman 09 Apr '10

09 Apr '10

traverse returns a plan, which is a list (ordered sequence) of op - component dotted pairs. Effectively, we can execute the plan by mapping PERFORM over it. This is strictly from memory. Hth. "Faré" <fahree(a)gmail.com> wrote: >Ahem. I admit this is a part of ASDF I am not familiar with. > >What does traverse return? Can you trace every exported defgeneric in >ASDF and attach to a launchpad bug traces of what happens in either >ASDF 1 or ASDF 2? > >Sorry I'm not being very helpful. > >[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] > \|/ ____ \|/ > ~@-/ oO \-@~ > /_( \__/ )_\ > \__U_/ > > > > >On 9 April 2010 23:45, Mario S. Mommer <m_mommer(a)yahoo.com> wrote: >> >> Faré <fahree(a)gmail.com> writes: >>> Does it work better with ASDF 1.672? If not, you might have to define >>> some method for operation-done-p or some such. >> >> No, unfortunately it does not work better. >> >> And operation-done-p is returning T's and NIL's with the new asdf as >> well as with the one packaged with sbcl, but the latter simply does not >> take that as a reason to recompile the lisp files, while the former >> does, or recompiles them for some other reason. >> >> Regards, >> Mario >> >> >> >> _______________________________________________ >> asdf-devel mailing list >> asdf-devel(a)common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel >> > >_______________________________________________ >asdf-devel mailing list >asdf-devel(a)common-lisp.net >http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.

1 0

[asdf-devel] pathname translations does not like my f2cl asd
by m_mommer＠yahoo.com 09 Apr '10

09 Apr '10

Hi, so here is another one. I can send the .asd file if you are interested, but for now I guess this snippet is enough: (defmethod perform ((o compile-op) (f f77-file)) (apply #'f2cl:f2cl-compile (cons (make-pathname :name (component-name f) :type "f" :defaults (component-pathname f)) (compiler-options f)))) the error is Couldn't load #P"/home/mommer/.cache/common-lisp/sbcl-1.0.37-linux-...": file does not exist. [Condition of type SB-INT:SIMPLE-FILE-ERROR] which is caused by the fact that I give the f2cl compiler a different output path than that expected by the loader. I do not know how to fix this yet, except for issuing (asdf:disable-output-translation). It is probably a matter of RTFM. But I guess that proves the more general point that enabling the output translation by default will break existing setups when upgrading. Regards, Mario

2 2

[asdf-devel] 1.671 compiles in abc, acl, ccl, ecl, cmucl, sbcl, lw
by james anderson 08 Apr '10

08 Apr '10

asdf@ip-10-251-122-82:/development/source/library$ /development/bin/ abcl --load build-init.lisp Armed Bear Common Lisp 0.19.1 Java 1.6.0_0 Sun Microsystems Inc. OpenJDK Client VM Low-level initialization completed in 0.963 seconds. Startup completed in 2.205 seconds. ; Compiling /ebs/source/library/net/common-lisp/asdf/asdf.lisp ... ; [ ... ] ; Wrote /ebs/source/library/net/common-lisp/asdf/asdf.abcl (13.859 seconds) Type ":help" for a list of available commands. CL-USER(1): asdf@ip-10-251-122-82:/development/source/library$ /development/bin/ alisp -qq -L build-init.lisp ;Build root: #P"/ebs/source/library/build-init.lisp". ;Incorporating asdf anew from #P"/ebs/source/library/net/common-lisp/ asdf/asdf.lisp". ;;; Compiling file /ebs/source/library/net/common-lisp/asdf/asdf.lisp ; [...] ;;; Writing fasl file /ebs/source/library/net/common-lisp/asdf/asdf.fasl ;;; Fasl write complete ;;; [ ... ] CL-USER(1): EOF Really exit lisp [n]? ; Exiting asdf@ip-10-251-122-82:/development/source/library$ /development/bin/ clisp -i build-init.lisp i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8 Welcome to GNU CLISP 2.48+ (2009-08-24) <http://clisp.cons.org/> Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2009 Type :h and hit Enter for context help. ;; Loading file build-init.lisp ... ;Build root: #P"/ebs/source/library/build-init.lisp". ;Incorporating asdf anew from #P"/ebs/source/library/net/common-lisp/ asdf/asdf.lisp". ;; Compiling file /ebs/source/library/net/common-lisp/asdf/asdf.lisp ... ;; Wrote file /ebs/source/library/net/common-lisp/asdf/asdf.fas 0 errors, 0 warnings ;; Loading file /ebs/source/library/net/common-lisp/asdf/asdf.fas ... ;; Loaded file /ebs/source/library/net/common-lisp/asdf/asdf.fas ;; [ ... ] [1]> Bye. asdf@ip-10-251-122-82:/development/source/library$ ccl --no-init -l build-init.lisp ;Build root: #P"/ebs/source/library/build-init.lisp". ;Incorporating asdf anew from #P"/ebs/source/library/net/common-lisp/ asdf/asdf.lisp". ;Compiling "/ebs/source/library/net/common-lisp/asdf/asdf.lisp"... ;Loading #P"/ebs/source/library/net/common-lisp/asdf/asdf.lx32fsl"... ;Loading #P"/ebs/source/library/de/setf/utility/asdf/hierarchical- names.lisp"... ;Loading #P"/ebs/source/library/de/setf/utility/pathnames.lisp"... ;Loading #P"/ebs/source/library/de/setf/utility/package.lisp"... Host translations: LIBRARY base: #P"/ebs/source/library/de/setf/utility/pathnames.lisp". location: NIL. root-target: #P"/ebs/source/library/**/*.*". binary: #P"/ebs/source/library/bin/omcl/**/*.lx32fsl". Welcome to Clozure Common Lisp Version 1.4-r13119 (LinuxX8632)! ? asdf@ip-10-251-122-82:/development/source/library$ /development/bin/ cmucl -load build-init.lisp ; Loading #P"/ebs/source/library/build-init.lisp". ;Build root: #P"/ebs/source/library/build-init.lisp". ; Python version 1.1, VM version Intel x86 on 08 APR 10 10:32:32 pm. ; Compiling: /ebs/source/library/net/common-lisp/asdf/asdf.lisp 08 APR 10 10:26:56 pm ; [ ... ]. ; /ebs/source/library/net/common-lisp/asdf/asdf.sse2f written. ; Compilation finished in 0:00:06. ;Incorporating asdf anew from #P"/ebs/source/library/net/common-lisp/ asdf/asdf.lisp". ;; Loading #P"/ebs/source/library/net/common-lisp/asdf/asdf.sse2f". ; [GC threshold exceeded with 19,203,144 bytes in use. Commencing GC.] ; [GC completed with 2,603,824 bytes retained and 16,599,320 bytes freed.] ; [GC will next occur when at least 14,603,824 bytes are in use.] CMU Common Lisp 20a (20A), running on ip-10-251-122-82 With core: /development/downloads/cmucl-20a-non-unicode-x86-linux/lib/ cmucl/lib/lisp-sse2.core Dumped on: Mon, 2009-09-28 16:06:53Z on usrtc3154 See <http://www.cons.org/cmucl/> for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2008-11-12 16:36:41 * (quit) asdf@ip-10-251-122-82:/development/source/library$ /development/bin/ ecl -load build-init.lisp ;;; Loading "/ebs/source/library/build-init.lisp" ;Build root: #P"/ebs/source/library/build-init.lisp". ;Incorporating asdf anew from #P"/ebs/source/library/net/common-lisp/ asdf/asdf.lisp". ;;; Loading #P"/development/lib/ecl-10.2.1/cmp.fas" ;;; Loading #P"/development/lib/ecl-10.2.1/sysfun.lsp" ;;; ;;; Compiling /ebs/source/library/net/common-lisp/asdf/asdf.lisp. ;;; [...] ;;; Note: ;;; Invoking external command: ;;; gcc -o "/ebs/source/library/net/common-lisp/asdf/asdf-ecl.fas" - L"/development/lib/" "/ebs/source/library/net/common-lisp/asdf/asdf- ecl.o" -shared -lecl -lgmp -ldl -lm ;;; ;;; Finished compiling /ebs/source/library/net/common-lisp/asdf/asdf- ecl.lisp. ;;; ;;; Loading "/ebs/source/library/net/common-lisp/asdf/asdf-ecl.fas" ;;; Loading "/ebs/source/library/de/setf/utility/asdf/hierarchical- names.lisp" ;;; Loading "/ebs/source/library/de/setf/utility/asdf/../pathnames.lisp" ;;; Loading "/ebs/source/library/de/setf/utility/asdf/../package.lisp" ;;; OPTIMIZE levels: Safety=3, Space=0, Speed=2, Debug=2 ;;; ;;; End of Pass 1. ;;; Note: ;;; Invoking external command: ;;; gcc "-I/development/include/" -D_GNU_SOURCE - D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -Dlinux -O -w -c "/tmp/ ECL001G986OB.c" -o "/tmp/ECL001G986OB.o" ;;; ;;; Note: ;;; Invoking external command: ;;; gcc -o "/tmp/ECL001G986OB.fas" -L"/development/lib/" "/tmp/ ECL001G986OB.o" -shared -lecl -lgmp -ldl -lm ;;; Host translations: LIBRARY base: #P"/ebs/source/library/de/setf/utility/pathnames.lisp". location: NIL. root-target: #P"/ebs/source/library/**/*.*". binary: #P"/ebs/source/library/bin/ECL/**/*.fas".ECL (Embeddable Common-Lisp) 10.2.1 Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya Copyright (C) 1993 Giuseppe Attardi Copyright (C) 2000 Juan J. Garcia-Ripoll ECL is free software, and you are welcome to redistribute it under certain conditions; see file 'Copyright' for details. Type :h for Help. Top level. > asdf::*asdf-version* "1.671" > asdf@ip-10-251-122-82:/development/source/library$ /usr/local/bin/ sbcl --no-sysinit --userinit build-init.lisp This is SBCL 1.0.36, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. ;Build root: #P"/ebs/source/library/". ;Incorporating asdf anew from #P"/ebs/source/library/net/common-lisp/ asdf/asdf.lisp". ; compiling file "/ebs/source/library/net/common-lisp/asdf/ asdf.lisp" (written 08 APR 2010 10:26:56 PM): ; compiling (IN-PACKAGE :CL-USER) ; compiling (DECLAIM (OPTIMIZE # ...)) ; compiling (LET* (# # ...) ...) ; file: /ebs/source/library/net/common-lisp/asdf/asdf.lisp ; [ ... ] ; /ebs/source/library/net/common-lisp/asdf/asdf.fasl written ; compilation finished in 0:00:05.487 ; loading #P"/ebs/source/library/net/common-lisp/asdf/asdf.fasl" ; loading #P"/ebs/source/library/de/setf/utility/asdf/hierarchical- names.lisp" ;; loading #P"/ebs/source/library/de/setf/utility/asdf/../ pathnames.lisp" ;;; loading #P"/ebs/source/library/de/setf/utility/asdf/../package.lisp" Host translations: LIBRARY base: #P"/ebs/source/library/de/setf/utility/pathnames.lisp". location: NIL. root-target: #P"/ebs/source/library/**/*.*". binary: #P"/ebs/source/library/bin/sbcl-linux/**/*.fasl". * asdf@ip-10-251-122-82:/development/source/library$ lispworks LispWorks(R): The Common Lisp Programming Environment Personal Edition Copyright (C) 1987-2008 LispWorks Ltd. All rights reserved. Version 5.1.1 Saved by LispWorks as lispworks-personal-5-1-1-x86-linux, at 13 May 2008 17:15 User asdf on ip-10-251-122-82 Error: Could not register handle for external module X- UTILITIES::CAPIX11: libXm.so.3: cannot open shared object file: No such file or directory. 1 (abort) Quit process. Type :b for backtrace, :c <option number> to proceed, or :? for other options CL-USER 1 : 1 > (load "build-init.lisp") ; Loading text file /ebs/source/library/build-init.lisp ;Build root: #P"/ebs/source/library/build-init.lisp". ;Incorporating asdf anew from #P"/ebs/source/library/net/common-lisp/ asdf/asdf.lisp". ;;; Compiling file /ebs/source/library/net/common-lisp/asdf/ asdf.lisp ... ;;; Safety = 3, Speed = 1, Space = 1, Float = 1, Interruptible = 0 ;;; Compilation speed = 1, Debug = 2, Fixnum safety = 3 ;;; [ ... ] ; Loading fasl file /ebs/source/library/net/common-lisp/asdf/asdf.ufasl #P"/ebs/source/library/build-init.lisp" CL-USER 2 : 1 >

1 0

[asdf-devel] duplicate-name condition
by Tobias C. Rittweiler 07 Apr '10

07 Apr '10

I was just bitten by a duplicate-name condition. It was on ASDF1, but the code still seems to be exactly the same in ASDF2. Please add a proper error message to that condition. I first thought there are two systems with the same name, but it actually complains about two files with the same name in the same component. -T.

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