From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail.clark.net ([168.143.0.10]) by hawkwind.utcs.utoronto.ca with SMTP id <24628>; Sun, 9 Mar 1997 00:31:59 -0500
Received: from explorer2.clark.net (culliton@explorer2.clark.net [168.143.0.5]) by mail.clark.net (8.8.5/8.6.5) with ESMTP id AAA06055; Sun, 9 Mar 1997 00:31:53 -0500 (EST)
From:	Tom Culliton <culliton@clark.net>
Received: (from culliton@localhost) by explorer2.clark.net (8.8.5/8.7.1) id AAA21257; Sun, 9 Mar 1997 00:31:40 -0500 (EST)
Date:	Sun, 9 Mar 1997 00:31:40 -0500
Message-Id: <199703090531.AAA21257@explorer2.clark.net>
To:	culliton@clark.net, tell@cs.unc.edu
Cc:	rc@hawkwind.utcs.toronto.edu
Subject: Re: rc, signals, readline, and Linux

> On Wed, 5 Mar 1997, Tom Culliton wrote:

> > So my big **** eating grin might tell you something. 8-)  Thats right,
> > unless I've overlooked something really dumb, it's fixed!!!  This fix
>
> I've been trying to get rc going on my new linux box recently; 
> Tom's patches definitely help a lot.  SIGINT definitely works properly with
> readline now.  This is enough improvement that I've installed it as my
> default. 
>
> All is not quite perfect, however.
>
> "make trip" hang on the first line in the history section:
>
> history=/tmp/hist.$pid prompt='' echo 'history=()' | $rc -i
>
> No history file is created in /tmp, and "./rc -i" is looping burning
> cpu cycles.   

Yeah, I reported this earlier.  You must ahve either missed the
message or it was one of the ones that bounced from the list.  For
some reason this problem occurs with readline under Linux if you don't
link statically.  Go back and look at my configuration patches which
include the proper link switches to make this happen.  What is needed
is somthing like:

	LDFLAGS= -static -lreadline -ltermcap

	:
	:

	rc: $(OBJS)
		$(CC) -o $@ $(OBJS) $(LDFLAGS)

With this rc should trip flawlessly.  I spent a bunch of time fiddling
with it, saw the same stack traces, but decided in the end that it had
already cost enough brain cells, and I really didn't give a hoot if
the binary was statically linked or not.  I'll leave that one for
someone else, who has more experience with dynamic linking under Linux
to solve. ;-) ;-) ;-)

Tom