From: Tom Culliton <culliton@clark.net>
To: Tim Goodwin <tgoodwin@cygnus.co.uk>
Cc: Tom Culliton <culliton@clark.net>, rc@hawkwind.utcs.toronto.edu
Subject: Re: rc,linux,signal,readline
Date: Wed, 13 Aug 1997 10:20:34 -0400 [thread overview]
Message-ID: <199708131420.KAA02857@clark.net> (raw)
In-Reply-To: Your message of "Wed, 13 Aug 1997 14:33:53 BST." <ZAoAAMG38TPctAEA@nan.cygnus.co.uk>
On Wed, 13 Aug 1997 14:33:53 BST, Tim Goodwin wrote:
> Sorry, I got lost here. What exactly is the problem? I just built
> rc-1.5b2 (now available from the usual FTP site, thanks Chris!)
> dynamically linked with readline...
Hmmm... I couldn't get the rc-1.5b2 distribution to do that under the
same version of Linux you say you're using. It claims it can't find
-lreadline. (It's there in /usr/lib/readline.* dammit!) Hacking it
into config.h and Makefile by hand seems to work.
> ; ldd rc
> libtermcap.so.2 => /lib/libtermcap.so.2.0.8
> libreadline.so.2 => /usr/lib/libreadline.so.2.0
> libc.so.5 => /lib/libc.so.5.3.12
>
> ...and it all seems to work ok. Specifically, INTs and QUITs work as I
> expect. Can you let me know what to look for so I can fix it?
Well lets see, for starters it hangs doing a "make trip" which is the
basic symptom I remember for the shared libraries. My recollection
was that this was usually associated with waiting for a prompt from a
subshell, or something like that. Hmmm, this actually looks a bit
different, maybe something else is interfering... I'll get back to
you on this...
Tom
next prev parent reply other threads:[~1997-08-13 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-12 8:19 rc,linux,signal,readline Russell Davies
1997-08-12 9:42 ` rc,linux,signal,readline Tim Goodwin
1997-08-12 13:59 ` rc,linux,signal,readline Tom Culliton
1997-08-12 21:24 ` rc,linux,signal,readline Paul Haahr
1997-08-12 21:55 ` rc,linux,signal,readline Tom Culliton
1997-08-13 13:33 ` rc,linux,signal,readline Tim Goodwin
1997-08-13 14:20 ` Tom Culliton [this message]
1997-08-13 17:57 ` rc,linux,signal,readline Tom Culliton
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=199708131420.KAA02857@clark.net \
--to=culliton@clark.net \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=tgoodwin@cygnus.co.uk \
/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).