public inbox for gentoo-lisp@lists.gentoo.org
 help / color / mirror / Atom feed
From: grozin@gentoo.org
To: gentoo-lisp@lists.gentoo.org
Subject: [gentoo-lisp] uiop
Date: Sat, 13 Apr 2013 12:06:53 +0700 (NOVT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1304131200350.28179@elrond.inp.nsk.su> (raw)

asdf-2.33-r2 installs uiop-2.33 which is supposewd to provide a 
compatibility with an old asdf. I thought, maybe, loading it before 
sb-posix can help. No:

grozin@dns ~ $ sbcl
This is SBCL 1.1.6, 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.
* (require :uiop)
ASDF could not load uiop because invalid number of arguments: 3.

debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR:
   invalid number of arguments: 3

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [TRY-RECOMPILING] ASDF could not load uiop because
                        There is no applicable method for the generic 
function
                          #<STANDARD-GENERIC-FUNCTION
                            ASDF/COMPONENT:COMPONENT-NAME (0)>
                        when called with arguments

debugger invoked on a SIMPLE-ERROR:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION ASDF/COMPONENT:COMPONENT-NAME (0)>
   when called with arguments
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-CONDITION* 
when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was 
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [RETRY          ] Retry calling the generic function.
   1:                   Retry calling the generic function.
   2: [TRY-RECOMPILING]

debugger invoked on a SIMPLE-ERROR:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION ASDF/COMPONENT:COMPONENT-NAME (0)>
   when called with arguments
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-CONDITION* 
when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was 
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [RETRY          ] Retry calling the generic function.
   1:                   Retry calling the generic function.
   2:                   Retry calling the generic function.
   3: [TRY-RECOMPILING]

debugger invoked on a SIMPLE-ERROR:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION ASDF/COMPONENT:COMPONENT-NAME (0)>
   when called with arguments
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-CONDITION* 
when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was 
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [RETRY          ] Retry calling the generic function.
   1:                   Retry calling the generic function.
   2:                   Retry calling the generic function.
   3:                   Retry calling the generic function.
   4: [TRY-RECOMPILING]

debugger invoked on a SIMPLE-ERROR:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION ASDF/COMPONENT:COMPONENT-NAME (0)>
   when called with arguments
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-CONDITION* 
when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was 
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [RETRY          ] Retry calling the generic function.
   1:                   Retry calling the generic function.
   2:                   Retry calling the generic function.
   3:                   Retry calling the generic function.
   4:                   Retry calling the generic function.
   5: [TRY-RECOMPILING]

debugger invoked on a SIMPLE-ERROR:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION ASDF/COMPONENT:COMPONENT-NAME (0)>
   when called with arguments
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-CONDITION* 
when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was 
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [RETRY          ] Retry calling the generic function.
   1:                   Retry calling the generic function.
   2:                   Retry calling the generic function.
   3:                   Retry calling the generic function.
   4:                   Retry calling the generic function.
   5:                   Retry calling the generic function.
   6: [TRY-RECOMPILING]

debugger invoked on a SIMPLE-ERROR:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION ASDF/COMPONENT:COMPONENT-NAME (0)>
   when called with arguments
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-CONDITION* 
when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was 
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [RETRY          ] Retry calling the generic function.
   1:                   Retry calling the generic function.
   2:                   Retry calling the generic function.
   3:                   Retry calling the generic function.
   4:                   Retry calling the generic function.
   5:                   Retry calling the generic function.
   6:                   Retry calling the generic function.
   7: [TRY-RECOMPILING]

debugger invoked on a SIMPLE-ERROR:
   There is no applicable method for the generic function
     #<STANDARD-GENERIC-FUNCTION ASDF/COMPONENT:COMPONENT-NAME (0)>
   when called with arguments
Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {1002940B93}>
Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {1002940B93}>
;
; compilation unit aborted
;   caught 1 fatal ERROR condition
*

Andrey


                 reply	other threads:[~2013-04-13  5:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.00.1304131200350.28179@elrond.inp.nsk.su \
    --to=grozin@gentoo.org \
    --cc=gentoo-lisp@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox