Sorry to bombard you folks with this, but I am pissed off and happy all at the same time. It seems that install.lisp was MISSING some brackets ... So, I got this far, and now, have what is hopefully the last issue:
CL-USER 5 > (load "c:/aa/asdf-install/asdf-install/load-asdf-install.lisp") ; Loading text file c:\aa\asdf-install\asdf-install\load-asdf-install.lisp ;;; ASDF-INSTALL: Loading ASDF-INSTALL package from directory ;;; "c:\aa\asdf-install\asdf-install"
; Loading text file c:\aa\asdf-install\asdf-install\defpackage.lisp ; Loading text file c:\aa\asdf-install\asdf-install\port.lisp ; Loading text file c:\aa\asdf-install\asdf-install\split-sequence.lisp ; Loading text file c:\aa\asdf-install\asdf-install\variables.lisp ; Loading text file c:\aa\asdf-install\asdf-install\conditions.lisp ; Loading text file c:\aa\asdf-install\asdf-install\installer.lisp #P"c:/aa/asdf-install/asdf-install/load-asdf-install.lisp"
CL-USER 6 > (require 'asdf) NIL
CL-USER 7 > (require 'asdf-install) NIL
CL-USER 8 > (asdf-install:install "c:/libraries/cl-ppcre.tar.gz") Install where? 1) System-wide install: System in \usr\local\asdf-install\site-systems\ Files in \usr\local\asdf-install\site\ 2) Personal installation: System in H:.asdf-install-dir\systems\ Files in H:.asdf-install-dir\site\ 0) Abort installation. --> 2 ;;; ASDF-INSTALL: Installing c:/libraries/cl-ppcre.tar.gz in H:.asdf-install-dir\site, H:.asdf-install-dir\systems\
Error: In ZEROP of (:ACTIVE) arguments should be of type NUMBER. 1 (continue) Return a value to use. 2 Supply a new argument. 3 (abort) Return to level 0. 4 Return to top loop level 0.
Type :b for backtrace or :c <option number> to proceed. Type :bug-form "<subject>" for a bug report template or :? for other options.
CL-USER 9 : 1 >
======================================================
It appears to have created the directories in H:.asdf-install-dir\ but there is nothing in those directories...
Thanks, Alex.
_______________________________________________________________________
This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message.
Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen.
What are you trying to do? Are you simply trying to get cl-ppcre to work under PLWW?
If so, send me the url of where you downloaded it (so that I'm working with exactly the same code) and I will make it compile under LWW and send you the fixes some time this afternoon.
Trying to fix asdf problems is WAY too frustrating, until you have more experience with LW under your belt. You might actually be hitting a bug in the release, which needs to be explored and reported to Edi. Don't waste your time.
pt
You can read below if you wish (I aborted the explanation and then wrote the above) ... ...
Error: In ZEROP of (:ACTIVE) arguments should be of type NUMBER.
...
The error message says that there was a call (ZEROP :ACTIVE). Indeed, :ACTIVE is a keyword, which evaluates to itself and is or type symbol, i.e. not a number.
It looks like you've hit a spot where LW error checking is more strict than whatever lisp was used to make this release (of asdf?).
Get to the point where you get the error, then hit the toolbar button that looks like a bug (Start GUI Debugger). This should show you the traceback GUI. Double-click on the function name closest to the top and this should position your cursor on the line in question (there might be one or two debugger functions at the very top of the traceback, so you might need to try a few of the topmost functions).
From the context, you might see how to fix the bug, e.g. maybe something like
(if (symbolp xx) (if (eq :ACTIVE xx) ...
When you get frustrated, remember that asdf only loads the files. You can do this yourself manually. Look at the asdf file, it should be obvious which files are being loaded, then load them into the editor one by one and hit the 'compile and load' toolbar button.
You are beginning to discover why people think that quicklisp is such a big deal - too bad that your firewalls prevent you from using it.
-
Matijaca, Aleksandar -
Paul Tarvydas