Re: How I Built scsh 0.7 from Github (for Newbies)

Norman Gray <[email protected]> Sat, 13 Oct 2012 11:51:13 +0100
Newsgroups gmane.lisp.scheme.scsh
Message-ID <[email protected]>
Greetings.

On 13 Oct 2012, at 10:13, RT Happe <[email protected]> wrote:

> Norman Gray 2012-10-13:
>> the message Does Not Appear To Be On The Web.
>> The scsh-users archive ... stops in 2007,
>> and the message doesn't appear to be anywhere else.
>=20
> Fear not, since the message lives on in the gmane archive / mirror;=20
> --> http://article.gmane.org/gmane.lisp.scheme.scsh/7817

Aha -- sanity is restored.  Thanks.

Unfortunately, I'd got that far myself.  My problem is that I'm trying =
to install somewhere other than /usr/local.

But I've since resolved that problem.  The following recipe works in =
that case:

----

Get s48 v1.8 from s48.org, build, and install it.=20
This is required in order to bootstrap current s48.

Get, build and install current s48, from =
<http://s48.org/cgi-bin/hgwebdir.cgi/s48>

  % hg clone http://s48.org/cgi-bin/hgwebdir.cgi/s48
  % PATH=3D/Data/tools/scsh-from-github/bin:$PATH ./autogen.sh
  % ./configure --prefix=3D$T/scsh-bleeding-edge
  % make
  % make install-no-doc

Now get scsh (see the docs on <https://github.com/scheme/scsh>):

  % git clone https://github.com/scheme/scsh.git
  % git submodule update --init
  % autoreconf
  % PATH=3D$T/scsh-bleeding-edge/bin:$PATH ./configure =
--prefix=3D$T/scsh-bleeding-edge \
        CFLAGS=3D-I$T/scsh-bleeding-edge/include\ -g\ -O2
  % make SCHEME48=3D$T/scsh-bleeding-edge/bin/scheme48 =
SCHEME48VM=3D/Data/tools/scsh-bleeding-edge/lib/scheme48-1.9t/scheme48vm =
install

Parenthetically, it'd be nice if there were a --with-scheme48=3Dpath =
option supported in configure.ac -- that's the sort of place I'd expect =
to configure the path gymnastics.

----

So far so good.  But when I run this on a scsh script which was working =
with 0.6.*, and which I invoke with "-o srfi-8 -o srfi-37 -e main ", I =
get

error: unhandled upcall [propogate-upcall]
       #{upcall-token user-session}

(I presume the spelling error is now a necessary fixture (although it =
makes it easier to google, I suppose)).  I've no idea where I'd start =
debugging this -- is it likely to be something which is the result of =
the odd location for scsh?

Best wishes,

Norman


--=20
Norman Gray  :  http://nxg.me.uk
SUPA School of Physics and Astronomy, University of Glasgow, UK