asdf-devel November 2010

asdf-devel@common-lisp.net

7 participants
10 discussions

[asdf-devel] New version of the here-directive topic branch pushed
by Robert Goldman 29 Nov '10

29 Nov '10

Note that this is not a fast-forward push, because it was rebased on top of Faré's latest version of ASDF on master. cheers, r

1 0

[asdf-devel] Pushed :here-directive topic branch
by Robert Goldman 29 Nov '10

29 Nov '10

This branch has patches that add the :here directive to Faré's configuration DSL. This allows for configuration files to have contents like: (:source-registry (:tree (:here "src/lisp/")) (:tree (:here "extlib/lisp")) (:directory (:here "outlier/"))) ... which means if, for instance, I have a source repo with a complex set of directories and .asd files, I can commit a .conf file into the repo and tell you just to "source" it through ASDF, and you'll automagically see all the .asd files in the directory. This is particularly useful when you don't want people to have to have ASDF grovel over the entire source tree in their working directories. I have found this to be desirable, as I often work in source trees that contain not just lisp code, but Java code (which generates /very/ big trees to search) and data files. I think this meets Faré's design principle that "everyone can specify what he knows, but doesn't have to specify what he doesn't know." I am checking this in on a topic branch for easy inspection before inclusion (I hope). The new feature of the DSL is also documented in the texinfo manual. Cheers, r

4 8

[asdf-devel] ASDF 2.011
by Faré 29 Nov '10

29 Nov '10

Dear Lispers, I'm pleased to announce the release of ASDF 2.011. As compared to ASDF 2.010, it only sports a series of minor changes, which I think is sign of ASDF 2 becoming mature: * minor portability tweaks, to make GCL (2.010.1) and Allegro (2.010.5) happy * minor fixes, to an error in error (2.010.8) * minor API cleanups, exporting symbol operation-description (2.010.6) and accepting keywords as component class names (2.010.3) * minor internal refactoring (2.010.4, 2.010.7 + 2.010.9) * minor improvement in dealing with incompatibility, refusing to run if asdf-binary-locations was loaded as it only works with asdf 1, with useful error message (2.010.7) * minor improvements in compatibility with cl-launch (2.010.2) and xcvb (2.010.4) If you missed it, 2.010 had a notable speedup in addition to minor fixes. It would be very nice of vendors to update the version of ASDF they ship with their respective implementations, or to start shipping it when they don't do it yet (LispWorks, SCL; Corman, GCL - if they are still being developed). PS: I think we should create an asdf-announce mailing-list so that vendors may subscribe to it and only get traffic relevant to releases. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Every technique is first developed, then used, important, obsolete, normalized, and finally understood.

1 0

[asdf-devel] poor error reporting in ASDF
by Cyrus Harmon 23 Nov '10

23 Nov '10

Dear ASDF developers, While trying to load a project of mine that depends on alexandria on a box that didn't have alexandria installed, I got the attached error message. It would be nice if there were better reporting letting one know that the dependency was not satisfied. thanks, Cyrus There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION ASDF:COMPONENT-NAME (1)> when called with arguments (#:ALEXANDRIA). [Condition of type SIMPLE-ERROR] Restarts: 0: [RETRY] Retry calling the generic function. 1: [ABORT] Return to sldb level 1. 2: [RETRY] Retry SLIME REPL evaluation request. 3: [*ABORT] Return to SLIME's top level. 4: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {1002FA0451}>) Backtrace: 0: ( ) 1: (SB-PCL::CALL-NO-APPLICABLE-METHOD ) 2: (ASDF::COMPONENT-FIND-PATH ) 3: ( ) 4: ( ) 5: (SB-IMPL::STRINGIFY-OBJECT ) 6: (PRINC-TO-STRING ) 7: (SWANK::FORMAT-RESTARTS-FOR-EMACS) 8: (SWANK:DEBUGGER-INFO-FOR-EMACS 0 20) 9: (SWANK::CALL-WITH-BINDINGS ) 10: (SWANK::SLDB-LOOP 1) 11: ( ) 12: (SWANK::DEBUG-IN-EMACS ) 13: (SWANK:INVOKE-SLIME-DEBUGGER ) 14: (SWANK-BACKEND::CALL-WITH-BREAK-HOOK ) 15: ( ) 16: (SWANK:SWANK-DEBUGGER-HOOK ) 17: (SB-DEBUG::RUN-HOOK *DEBUGGER-HOOK* ) 18: (INVOKE-DEBUGGER ) 19: (ERROR ASDF:MISSING-DEPENDENCY :REQUIRED-BY :REQUIRES ) 20: (ASDF::%DO-ONE-DEP ASDF:COMPILE-OP NIL) 21: (ASDF::DO-ONE-DEP ASDF:COMPILE-OP NIL) 22: ( ASDF:COMPILE-OP NIL) 23: (ASDF::DO-DEP ASDF:COMPILE-OP ) 24: ( ) 25: (ASDF::DO-ONE-DEP ASDF:COMPILE-OP NIL) 26: ( ASDF:COMPILE-OP NIL) 27: (ASDF::DO-DEP ASDF:COMPILE-OP ) 28: ( ) 29: (ASDF::DO-ONE-DEP ASDF:COMPILE-OP NIL) 30: ( ASDF:COMPILE-OP NIL) 31: (ASDF::DO-DEP ASDF:COMPILE-OP ) 32: ( ) 33: ( ) 34: ( ASDF:LOAD-OP CHEMICL) ...

2 1

Re: [asdf-devel] [PROPOSAL] Easier configuration, installation, and removal of asdf systems
by Krzysztof Drewniak 20 Nov '10

20 Nov '10

On Sat, 2010-11-20 at 02:10 -0500, Faré wrote: > On 19 November 2010 16:20, Krzysztof Drewniak <krzysdrewniak(a)gmail.com> wrote: > >> 2- It's not clear that anyone would use it. What problem are you solving? > >> How does it help? > >> > > If solves the problem of not having a standard way to "install" a common > > lisp library. See my other reply for details. > > > There is nothing whatsoever to install in a CL library. > FASLs? They vary from implementation to implementation, > and even in a given implementation, depending on > OPTIMIZE settings, *features* and possibly more > (code coverage, grovelling, some lisp-in-lisp compilation > for e.g. continuations, etc.) > > And what the hell do you configuration settings correspond to? > Yet another layer of bureaucracy between the user and > the above-mentionned settings and features? > > > As fetching dependencies is clearly not in scope for asdf, dependencies > > will be checked to see if they are loadable in the beginning of > > install-op, and if they are not present, a helpful error is signalled. > > > What when a dependency is compiled with a different settings, entailing > different semantics for the final "library"? > > >> 4- How do you distinguish between fasls compiled with different options. > >> > > If config.asdf is modified, fasls are recompiled. If two different > > source trees of the same system are installed, they will vertanly not be > > installed in the same place, thuse distinguishing the fasls. > > > That's not the question asked. How do you make sure there is no unwanted > sharing between two "versions" of the fasls for a same library as installed > in the same tree? > > > Also, if you are using different "trees" of libraries, either use > > different :registry files, or don't use these operations. > > > That's not the question asked. If you have different trees, > you don't need to distinguish configurations. > But usually you don't. > > Or what the hell are your "configurations" useful for? > > > To clarify something in advance, config-get does NOT require you to have > > used install-op, you could have done the installation manually. > > > Your whole proposal sounds like more bureaucracy that doesn't actually > help anyone get anything done but adds more work for everyone. > I say emphatically NO to any of it. > > Please provide a use case — we'll tell you how to do without it. > > There are ways that a build system could benefit from understanding > multiple "configurations" of a same tree, but ASDF will never ever > possibly do that, since that would require major refactoring and > breaking backward compatibility. If you're interested in such things, > consider hacking XCVB instead. > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] > Big Business has to *sell* the Vietnam War to you. Big Government can just > draft your ass and ship you overseas under threat of imprisonment and/or > death. Now, which one is better again? — rho(a)netdoor.com Never mind. asdf-install already solved most of the problem. -- X-Real-Email-With-Antispam: krzysdrewniak at gmail dot com pgp key on keyserver.ubuntu.com 94F02AE8

1 0

[asdf-devel] How to load a lisp file containing non ascii characters encoded in utf-8?
by pjb＠informatimago.com 20 Nov '10

20 Nov '10

What should be done in abcl to be able to load a lisp file containing non ascii characters encoded in utf-8? CL-USER(3): (load "test.lisp") Error loading /home/pjb/test.lisp at line 2 (offset 46) #<THREAD "interpreter" {74CB02}>: Debugger invoked on condition of type STREAM-ERROR Input value 0xffc3 is malformed while recoding with charset US-ASCII Restarts: 0: TOP-LEVEL Return to top level. [1] CL-USER(4): (lisp-implementation-version) "0.20.0" test.lisp is: ------------------------------------------------------------------------ ;; -*- mode:lisp;coding:utf-8 -*- (defvar *a* "é") ------------------------------------------------------------------------ -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.

1 1

[asdf-devel] There is no way to compile abcl-src-0.22.0
by pjb＠informatimago.com 20 Nov '10

20 Nov '10

Armed Bear Common Lisp --> "0.20.0" Clozure Common Lisp --> "Version 1.6-RC1-r14432M (LinuxX8664)" CLISP --> "2.49 (2010-07-07) (built 3499053122) (memory 3499054130)" CMU Common Lisp --> "19c (19C)" ECL --> "10.7.1" SBCL --> "1.0.19-gentoo" [pjb@kuiper :0.0 abcl-src-0.22.0]$ sh build-from-lisp.sh abcl Armed Bear Common Lisp 0.20.0 Java 1.6.0_22 Sun Microsystems Inc. Java HotSpot(TM) Server VM Low-level initialization completed in 0.272 seconds. Startup completed in 0.71 seconds. Platform: Linux JDK: /opt/sun-jdk-1.6.0.22/ Java compiler: /opt/sun-jdk-1.6.0.22/bin/javac Compiler options: -g Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: JavaObject.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. Armed Bear Common Lisp 0.22.0 Java 1.6.0_22 Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.232 seconds. Startup completed in 2.678 seconds. #<THREAD "interpreter" {664310D0}>: Debugger invoked on condition of type ERROR Failed to find loadable system file 'system' in boot classpath. C-c C-c [pjb@kuiper :0.0 abcl-src-0.22.0]$ sh build-from-lisp.sh ccl ;Compiler warnings for "/data/src/languages/abcl/abcl-src-0.22.0/build-abcl.lisp" : ; In SAFE-NAMESTRING: Unused lexical variable LEN Platform: Linux JDK: /opt/sun-jdk-1.6.0.22/ Java compiler: /opt/sun-jdk-1.6.0.22/bin/javac Compiler options: -g Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: JavaObject.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. Armed Bear Common Lisp 0.22.0 Java 1.6.0_22 Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.227 seconds. Startup completed in 2.638 seconds. #<THREAD "interpreter" {548997D1}>: Debugger invoked on condition of type ERROR Failed to find loadable system file 'system' in boot classpath. [1] CL-USER(1): Build completed successfully in 7.132986 seconds. [pjb@kuiper :0.0 abcl-src-0.22.0]$ sh build-from-lisp.sh clisp ;; Loading file build-abcl.lisp ... ;; Loaded file build-abcl.lisp ;; Loading file /data/src/languages/abcl/abcl-src-0.22.0/customizations.lisp ... ;; Loaded file /data/src/languages/abcl/abcl-src-0.22.0/customizations.lisp Platform: gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES -I. -lreadline -lncurses -ldl -lavcall -lcallback -lsigsegv libgnu_cl.a SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.8 libreadline 6.0 JDK: /opt/sun-jdk-1.6.0.22/ Java compiler: /opt/sun-jdk-1.6.0.22/bin/javac Compiler options: -g Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: JavaObject.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. Armed Bear Common Lisp 0.22.0 Java 1.6.0_22 Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.233 seconds. Startup completed in 2.651 seconds. #<THREAD "interpreter" {1137D4A4}>: Debugger invoked on condition of type ERROR Failed to find loadable system file 'system' in boot classpath. [1] CL-USER(1): (quit) Build completed successfully in 11.080321 seconds. [pjb@kuiper :0.0 abcl-src-0.22.0]$ sh build-from-lisp.sh lisp ; Loading #P"/data/src/languages/abcl/abcl-src-0.22.0/build-abcl.lisp". ; In: LAMBDA (PATHNAME) ; (LET* (# #) ; (WHEN # ; #) ; STRING) ; Note: Variable BUILD-ABCL::LEN defined but never used. Platform: Linux ; [GC threshold exceeded with 12,010,408 bytes in use. Commencing GC.] ; [GC completed with 1,294,232 bytes retained and 10,716,176 bytes freed.] ; [GC will next occur when at least 13,294,232 bytes are in use.] JDK: /opt/sun-jdk-1.6.0.22/ Java compiler: /opt/sun-jdk-1.6.0.22/bin/javac Compiler options: -g Error in function UNIX::SIGSEGV-HANDLER: Segmentation Violation at #x0. [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Skip remaining initializations. Debug (type H for help) (UNIX::SIGSEGV-HANDLER #<unused-arg> #<unused-arg> #.(SYSTEM:INT-SAP #x3FFFC554)) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:code/signal.lisp. 0] (unix:unix-exit) Error in function UNIX::SIGSEGV-HANDLER: Segmentation Violation at #x0. [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Skip remaining initializations. Debug (type H for help) (UNIX::SIGSEGV-HANDLER #<unused-arg> #<unused-arg> #.(SYSTEM:INT-SAP #x3FFFC554)) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:code/signal.lisp. 0] (unix:unix-exit 1) Build completed successfully in 33.49 seconds. ; [pjb@kuiper :0.0 abcl-src-0.22.0]$ [pjb@kuiper :0.0 abcl-src-0.22.0]$ sh build-from-lisp.sh ecl ;;; Loading "/data/src/languages/abcl/abcl-src-0.22.0/build-abcl.lisp" ;;; Loading "/data/src/languages/abcl/abcl-src-0.22.0/customizations.lisp" Platform: Linux JDK: /opt/sun-jdk-1.6.0.22/ Java compiler: /opt/sun-jdk-1.6.0.22/bin/javac Compiler options: -g Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: JavaObject.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. Build failed. [pjb@kuiper :0.0 abcl-src-0.22.0]$ sh build-from-lisp.sh sbcl This is SBCL 1.0.19-gentoo, 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. ; loading system definition from ; /usr/share/common-lisp/systems/asdf-binary-locations.asd into ; #<PACKAGE "ASDF0"> ; registering #<SYSTEM ASDF-BINARY-LOCATIONS {1002BFE1B1}> as ; ASDF-BINARY-LOCATIONS ; in: LAMBDA NIL ; (LET* ((STRING (NAMESTRING PATHNAME)) (BUILD-ABCL::LEN (LENGTH STRING))) ; (WHEN (POSITION #\ STRING) ; (SETF STRING ; (CONCATENATE 'STRING "\"" (BUILD-ABCL::COMP STRING #\\) "\""))) ; STRING) ; ; caught STYLE-WARNING: ; The variable LEN is defined but never used. ; ; compilation unit finished ; caught 1 STYLE-WARNING condition Platform: Linux JDK: /opt/sun-jdk-1.6.0.22/ Java compiler: /opt/sun-jdk-1.6.0.22/bin/javac Compiler options: -g Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: JavaObject.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. Armed Bear Common Lisp 0.22.0 Java 1.6.0_22 Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.231 seconds. Startup completed in 2.547 seconds. #<THREAD "interpreter" {73EB904D}>: Debugger invoked on condition of type ERROR Failed to find loadable system file 'system' in boot classpath. [1] CL-USER(1): Build completed successfully in 7.044 seconds. [pjb@kuiper :0.0 abcl-src-0.22.0]$ -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.

1 1

[asdf-devel] [PROPOSAL] Easier configuration, installation, and removal of asdf systems
by Krzysztof Drewniak 19 Nov '10

19 Nov '10

Rationale: To make asdf easier to use by providing a standard interface for configuring, installing, and removing systems Details: To facilitate easier configuration, installation, and removal of asdf systems, I propose 2 new operations and 2 new functions be added. The operations would be install-op and remove-op, and the functions would be configure and config-of These new components would work as defined below: * New function: configure (defmethod configure (&rest options) ...) configure would, given a plist of options, print them to a file in the current directory (which is assumed to contain the asdf system to configure), for example `config.asdf'. If config.asdf already exists, it should be moved to config.asdf.bak before the mew config.asdf is written. * New operation: install-op install-op would, given a directory in which `configure' had been run, use the options given to configure to install the system. The options involved would be :sources and :registry . :sources is the pathname of a directory which is to be created, after which the contents of the current directory is copied into the directory named by :sources . After the files are copied, all .asd files in :sources are linked into the pathname located in :registry. It is an error to run install-op without first having called configure. * New function config-get (defmethod config-get (system config-key &optional default) ...) config-get will, given a system and config-key retrieve the value of config-key located in the config.asdf file located in the same director as the .asd file of the system (after dereferencing symlinks). This method is meant so that library/program authors can add additional configure options which the library/program can later access (Ex. a graphics library with an optional #d component could instruct users to pass `:3d t' or `:3d nil' depending on whether they want the 3d component. The user's choice would be accessed through config-get). The functions will return 2 values, the primary being the result of the lookup or default if the lookup fails, and a secondary which is T if the lookup succeeded and NIL otherwise. * New operation: remove-op remove-op would undo the operations preformed by install-op, first removing the symlinks in :registry then deleting :sources. Comments, suggestions, questions, etc. are appreciated. Krzysztof Drewniak [P.S. I will not be available between 09/22/2010 and 09/29/2010 due to a vacation resort in Mexico which has an 80% chance of no free Internet] -- X-Real-Email-With-Antispam: krzysdrewniak at gmail dot com pgp key on keyserver.ubuntu.com 94F02AE8

3 2

[asdf-devel] Directly loading "/home/etc/etc/system.asd"
by Theam Yong Chew 09 Nov '10

09 Nov '10

Hi all, Is there a way to load a system directly, leaving everything else (source-registry configuration, *central-registry*, or what not) alone? I hacked up something to do this, (asdf:load-system #P"c:/blah/blah/cl-ppcre-1.2.19/cl-ppcre.asd") so that there's no need to worry about specific versions or setting up paths to a specific library. If the library being loaded depends on other modules, then we return to searching the source-registry as if by typing this before loading our system: (asdf:load-system <lib-depended-upon>) Does asdf already support this? Will such a feature be useful? Yong.

2 1

[asdf-devel] ccl:rebuild-ccl and asdf
by R. Matthew Emerson 08 Nov '10

08 Nov '10

We've gotten a couple of bug reports from users who are having trouble doing (ccl:rebuild-ccl :clean t) when (require 'asdf) is in their init files. http://trac.clozure.com/ccl/ticket/765 http://trac.clozure.com/ccl/ticket/773 While it's undoubtedly best to start up without an init file when you're planning to rebuild the lisp (by using "ccl -n"), I'm wondering if there would be some way to avoid this particular issue involving ASDF. During the process of rebuilding ccl, we compile (but do not load) ccl:tools;asdf.lisp. Perhaps we could simply stop compiling ASDF as part of ccl:rebuild-ccl. That way, the compile-time side effects that seem to be causing the trouble would be avoided.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel November 2010