Colin Benson <·········@gmail.com> writes:
> I want to follow along with Eric Normand's LispCast 1
> (www.lispcast.com). I can
> get hunchentoot to start and display its default page but no
> further. I've tried downloading the complete source file from the
> website but to no effect. I still get the default web page. I wonder
> if this is to do with an error I saw while installing hunchentoot...
>
>
> on OS X (10.4.10) with SBCL (1.0.10) and Slime in the Carbon port of
> Emacs 22.1.1. At this point I'm such a Lisp, ASDF, ASDF-Install,
> Hunchentoot and Slime beginner than I probably don't even qualify for
> "dumb". Therefore your patience is appreciated.
>
> I fire up Emacs, M-x slime, then
>
> (require 'asdf)
> (require 'asdf-install)
> (asdf-install:install 'hunchentoot)
>
> Things progress for a few moments, then I get the errors shown
> below. What have I done wrong?
Hmmm. The error message isn't really very informative. One would
really wish for some better indication of why the compilation operator
failed. I wonder if you would get a better error message if we
eliminated the Emacs-Slime part of the system.
Try doing the same things directly in sbcl. Start up sbcl and then type
(or copy) those forms into the sbcl listener directly. (You should be
able to start sbcl in a Terminal window by just typing its name).
Maybe that will produce something more debuggable.
--
Thomas A. Russ, USC/Information Sciences Institute
···@sevak.isi.edu (Thomas A. Russ) writes:
> Hmmm. The error message isn't really very informative. One would
> really wish for some better indication of why the compilation operator
> failed. I wonder if you would get a better error message if we
> eliminated the Emacs-Slime part of the system.
No need to wonder. It won't be any better.
The real error message that triggered the failure will almost
certainly be somewhere in the previous compilation output.
> Try doing the same things directly in sbcl. Start up sbcl and then type
> (or copy) those forms into the sbcl listener directly. (You should be
> able to start sbcl in a Terminal window by just typing its name).
>
> Maybe that will produce something more debuggable.
Nope. It will mean scrolling back with xterm instead of emacs. That's
about it.
Zach
From: Edi Weitz
Subject: Re: LispCast, hunchentoot, SBCL, OS X.
Date:
Message-ID: <ur6j9x67t.fsf@agharta.de>
On Thu, 01 Nov 2007 08:30:12 -0700, Colin Benson <·········@gmail.com> wrote:
> I want to follow along with Eric Normand's LispCast 1
> (www.lispcast.com). I can get hunchentoot to start and display its
> default page but no further. I've tried downloading the complete
> source file from the website but to no effect. I still get the
> default web page. I wonder if this is to do with an error I saw
> while installing hunchentoot...
http://weitz.de/hunchentoot/#mail
--
Lisp is not dead, it just smells funny.
Real email: (replace (subseq ·········@agharta.de" 5) "edi")
On Nov 1, 10:30 am, Colin Benson <·········@gmail.com> wrote:
> I want to follow along with Eric Normand's LispCast 1
> (www.lispcast.com). I can
> get hunchentoot to start and display its default page but no
> further. I've tried downloading the complete source file from the
> website but to no effect. I still get the default web page. I wonder
> if this is to do with an error I saw while installing hunchentoot...
>
> on OS X (10.4.10) with SBCL (1.0.10) and Slime in the Carbon port of
> Emacs 22.1.1. At this point I'm such a Lisp, ASDF, ASDF-Install,
> Hunchentoot and Slime beginner than I probably don't even qualify for
> "dumb". Therefore your patience is appreciated.
>
> I fire up Emacs, M-x slime, then
>
> (require 'asdf)
> (require 'asdf-install)
> (asdf-install:install 'hunchentoot)
>
> Things progress for a few moments, then I get the errors shown
> below. What have I done wrong?
>
> Thanks
>
> c
>
I got everything to work by installing sbcl through darwinports, then
downloading and compiling sbcl from the source with threading turned
on. The INSTALL doc explains how to do this. Everything worked fine
after that. This works on an Intel machine, don't know about PPC.