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"))) ))
I have a hard time telling from the documentation what is even
supposed to happen in this case, but the implementation doesn't
support my intuition.
In particular, say that files "a" and "b" are already compiled and
up to date, but file "c" needs to be recompiled. If I do
(asdf:operate 'asdf:load-op "test")
I would expect that "a" and "b" get LOADed first, then "c" gets COMPILEd,
and finally the new compiled "c" gets LOADed.
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.
Thus it appears to me that requesting the top-level system be ":serial t"
isn't taking effect, as it ought to make "c" depend on "a" and "b", and
thus ought to load them before it tries compiling "c".
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
