From: Tom Culliton <culliton@clark.net>
To: culliton@clark.net, tell@cs.unc.edu
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc, signals, readline, and Linux
Date: Sun, 9 Mar 1997 00:31:40 -0500 [thread overview]
Message-ID: <199703090531.AAA21257@explorer2.clark.net> (raw)
> 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
next reply other threads:[~1997-03-09 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-09 5:31 Tom Culliton [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-03-05 5:55 Tom Culliton
1997-03-09 4:24 ` Stephen Tell
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=199703090531.AAA21257@explorer2.clark.net \
--to=culliton@clark.net \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=tell@cs.unc.edu \
/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;
as well as URLs for NNTP newsgroup(s).