rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: David Luyer <luyer@ucs.uwa.edu.au>
To: Tim Goodwin <tjg@star.le.ac.uk>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: New snapshot rc-1.5s19981211 available
Date: Thu, 6 May 1999 23:58:11 -0400	[thread overview]
Message-ID: <199905070358.LAA26862@typhaon.ucs.uwa.edu.au> (raw)
In-Reply-To: Your message of "Thu, 06 May 1999 12:03:52 -0400." <AAAdXTcxvWgADtD5@ltsun0.star.le.ac.uk>

> If anyone has Debian Linux handy, please can you try this snapshot, and
> confirm that, when configuring with readline, it correctly picks up
> `-lncurses'.

Debian Linux now has at least one problem - there's no names for singals
in /usr/include/asm/singal.h (just numbers!)

Also, last time I compiled a new rc, this hit me:

#define _NSIG             32
#define NSIG            _NSIG

(the script tries to work out how many signals)

It would be nice to get a message for programs exiting on signals once
again (long ago I made my rc compile with names for all 31 signals defined
under Linux; current Debian packages don't give messages for many if any).

David.

PS: I did an rc port to BeOS mwcc recently, but won't bother submitting the
changes, since BeOS have dropped mwcc I believe and making it work under
that was ugly.

One thing that showed up which might be useful is

#ifndef SIGCHLD
#define SIGCHLD SIGCLD
#endif



  reply	other threads:[~1999-05-07  5:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-06 16:03 Tim Goodwin
1999-05-07  3:58 ` David Luyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-12-11 17:09 Tim Goodwin

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=199905070358.LAA26862@typhaon.ucs.uwa.edu.au \
    --to=luyer@ucs.uwa.edu.au \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=tjg@star.le.ac.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).