Don Geddis wrote:
> Package: cl-asdf
> Version: 1.86-2
> Severity: normal
> 
> I've got a system definition something like this:
> (asdf:defsystem "test"
>   :serial t
>   :components
>       ((:module "one" :components ((:file "a") (:file "b")))
>        (:module "two" :components ((:file "c"))) ))

...
> Instead, the effect seems to be that "c" is compiled in the empty environment
> (leading to lots of spurious warnings about undefined functions), and only
> then are "a", "b", and "c" loaded.

Strange. When I try to create this it seems to work. I'll show you why I
think it should so you can see with your 'real' asdf file:

$ sbcl --userinit /dev/null
This is SBCL 0.8.21.16, 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.
* (load "test.asd")

T
* (inspect (asdf:find-system :test))

The object is a STANDARD-OBJECT of type ASDF:SYSTEM.
0. NAME: "test"
1. VERSION: "unbound"
2. IN-ORDER-TO: NIL
3. DO-FIRST: ((ASDF:COMPILE-OP (ASDF:LOAD-OP)))
4. INLINE-METHODS: NIL
5. PARENT: NIL
6. RELATIVE-PATHNAME: #P"/home/pvaneynd/tmp/"
7. OPERATION-TIMES: #<HASH-TABLE :TEST EQL :COUNT 0 {9171571}>
8. PROPERTIES: NIL
9. COMPONENTS: (#<ASDF:MODULE "one" {9187A21}> #<ASDF:MODULE "two" {918B4A9}>)
10. IF-COMPONENT-DEP-FAILS: :FAIL
11. DEFAULT-COMPONENT-CLASS: NIL
12. DESCRIPTION: "unbound"
13. LONG-DESCRIPTION: "unbound"
14. AUTHOR: "unbound"
15. MAINTAINER: "unbound"
16. LICENCE: "unbound"
> 9

The object is a proper list of length 2.
0. 0: #<ASDF:MODULE "one" {9187A21}>
1. 1: #<ASDF:MODULE "two" {918B4A9}>
> 1

The object is a STANDARD-OBJECT of type ASDF:MODULE.
0. NAME: "two"
1. VERSION: "unbound"
2. IN-ORDER-TO: ((ASDF:LOAD-OP (ASDF:LOAD-OP "one"))
                 (ASDF:COMPILE-OP (ASDF:COMPILE-OP "one")))
3. DO-FIRST: ((ASDF:COMPILE-OP (ASDF:LOAD-OP "one")))
4. INLINE-METHODS: NIL
5. PARENT: #<ASDF:SYSTEM "test" {9171379}>
6. RELATIVE-PATHNAME: NIL
7. OPERATION-TIMES: #<HASH-TABLE :TEST EQL :COUNT 0 {918B6F1}>
8. PROPERTIES: NIL
9. COMPONENTS: (#<ASDF:CL-SOURCE-FILE "c" {918B871}>)
10. IF-COMPONENT-DEP-FAILS: :FAIL
11. DEFAULT-COMPONENT-CLASS: NIL
>

Notice the do-first and in-order-to component?


Do you get the same makeup?

Groetjes, Peter


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to