Next deliver problem

When I load my system without delivery I get these warnings at
startup

| ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\bordeaux-threads.ofasl
| ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\lispworks.ofasl
| Warning: (METHOD
|           MAKE-THREAD
|           (T)) being redefined in d:\Projekte\Lisp\bordeaux-
| threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
| threads\src\bordeaux-threads.lisp).
| Warning: (METHOD
|           MAKE-LOCK
|           NIL) being redefined in d:\Projekte\Lisp\bordeaux-
| threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
| threads\src\bordeaux-threads.lisp).
| Warning: (DEFMACRO WITH-LOCK-HELD) being redefined in d:\Projekte\Lisp\bordeaux-
| threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
| threads\src\bordeaux-threads.lisp).
| Warning: (METHOD
|           THREAD-YIELD
|           NIL) being redefined in d:\Projekte\Lisp\bordeaux-
| threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
| threads\src\bordeaux-threads.lisp).

I don't understand why my settings try to load these definitions
twice.

The system works properly when loaded manually but does not work when loaded
with delivery. It simply stops at these warnings. My delivery options are

| (in-package :cl-user)
| (load-all-patches)
| (load "load")
| (deliver 'webcat::start "kasbas.exe" 0
|          :display-progress-bar nil
|          :multiprocessing t
|          :console :output
|          :analyse t)

Thanks for your patience.

Jens

Re: Next deliver problem

On Sat, 17 Nov 2007 15:11:46 +0100, "Jens Teich" <info@jensteich.de> wrote:

> When I load my system without delivery I get these warnings at
> startup
>
> | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\bordeaux-threads.ofasl
> | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\lispworks.ofasl
> | Warning: (METHOD
> |           MAKE-THREAD
> |           (T)) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).
> | Warning: (METHOD
> |           MAKE-LOCK
> |           NIL) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).
> | Warning: (DEFMACRO WITH-LOCK-HELD) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).
> | Warning: (METHOD
> |           THREAD-YIELD
> |           NIL) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).
>
> I don't understand why my settings try to load these definitions
> twice.
>
> The system works properly when loaded manually but does not work
> when loaded with delivery. It simply stops at these warnings. My
> delivery options are
>
> | (in-package :cl-user)
> | (load-all-patches)
> | (load "load")
> | (deliver 'webcat::start "kasbas.exe" 0
> |          :display-progress-bar nil
> |          :multiprocessing t
> |          :console :output
> |          :analyse t)
>
> Thanks for your patience.

Are you starting from a "fresh" image, i.e. from the one that is
distributed by LispWorks?  I could imagine that the image that you're
using for delivery (the one you're invoking with the "-init" option)
already has some libraries loaded.

If not, it would be interesting to know the contents of your
"load.lisp" file and how exactly you invoke delivery.

Edi.

PS: The reason that the delivery process stops at some point is most
    likely an idiosyncrasy of ASDF which simply gives up at some point
    if it has seen certain warnings.  AFAIK there's no easy workaround
    for this except for muffling these warnings.

Re: Next deliver problem

On Sat, 17 Nov 2007 16:40:52 +0100, "Jens Teich" <info@jensteich.de> wrote:

>> Are you starting from a "fresh" image, i.e. from the one that is
>> distributed by LispWorks?

Are you?

>> If not, it would be interesting to know the contents of your
>> "load.lisp" file and how exactly you invoke delivery.
                    ------------------------------------
                    ^

So?

Re: Next deliver problem

On Sat, 17 Nov 2007 15:11:46 +0100, "Jens Teich" <info@jensteich.de> wrote:

> When I load my system without delivery I get these warnings at
> startup
>
> | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\bordeaux-threads.ofasl
> | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\lispworks.ofasl
> | Warning: (METHOD
> |           MAKE-THREAD
> |           (T)) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).
> | Warning: (METHOD
> |           MAKE-LOCK
> |           NIL) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).
> | Warning: (DEFMACRO WITH-LOCK-HELD) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).
> | Warning: (METHOD
> |           THREAD-YIELD
> |           NIL) being redefined in d:\Projekte\Lisp\bordeaux-
> | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux-
> | threads\src\bordeaux-threads.lisp).

Sorry, I misread this message and thought you /only/ got these message
during delivery.  I just checked and the reason you get the messages
seems to be in fact that the methods are defined twice.  For example,
for MAKE-THREAD there's a DEFGENERIC in src/bordeaux-threads.lisp
which defines a method for (T) and in src/lispworks.lisp they again
define a method for (T).  You should report that to the authors.

(Or you shouldn't use bordeaux-threads at all.  IIUC it's a
portability layer, so if you're only developing for LW, you don't need
it.)

As to why delivery probably fails, see the "PS" in my first reply.

Re: Next deliver problem

On Sat, 17 Nov 2007 18:44:10 +0100, "Jens Teich" <info@jensteich.de> wrote:

> I looked up
> idiosyncrasy = Eigenart

Right.

> muffling     = umhüllen ???

  http://www.lispworks.com/documentation/HyperSpec/Body/a_muffle.htm

Re: Next deliver problem

On Sat, 17 Nov 2007 18:44:10 +0100, "Jens Teich" <info@jensteich.de> wrote:

> idiosyncrasy = Eigenart

In German there's also "Idiosynkrasie" BTW... :)