From: Stefan Dalibor <dalibor@caldera.de>
To: Tim Goodwin <tjg@star.le.ac.uk>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Release candidate rc-1.6c4 available
Date: Thu, 1 Nov 2001 12:35:03 -0500 [thread overview]
Message-ID: <20011101183503.A31677@caldera.de> (raw)
In-Reply-To: <20011031161824.1422.qmail@happy.star.le.ac.uk>; from tjg@star.le.ac.uk on Wed, Oct 31, 2001 at 11:18:24AM -0500
Hi,
On Wed, Oct 31, 2001 at 11:18:24AM -0500, Tim Goodwin wrote:
> A new beta release, which is also a release candidate for the next
> full release, is available from the usual place.
...
> I need your help to decide if this release candidate is a trick or a
> treat. I'm using this version (with GNU readline) on RedHat, SunOS,
> and Tru64. I've also built and tripped it on CygWin, Irix, NetBSD,
> and OpenBSD.
not very surprisingly, 1.6c4 builds and trips fine under OpenLinux
3.1.1, with and without GNU readline (this is
Linux 2.4.9/glibc-2.2.4/gcc-2.95.2).
QNX RTP 6.1.0 is a bit more problematic:
These are minor:
o utoa() in print.c conflicts with a library function (with different
signature) - renaming rc's version of the function fixes this
o test isn't delivered as standalone program with this OS, so the glob
test in trip.rc for many slashes fails - this can be fixed by
changing the resp. line to `sh -c 'test -f '^...'
These are worse:
o setrlimit() fails to inherit limits to child processes, i.e.
`limit coredumpsize 0; limit coredummpsize | cat' results in
`coredumpsize unlimited' - IMHO this is a bug in QNX as other shells
(bash2, pdksh) show the same bug
o the test for waiting for a killed process fails too - rc's wait
exits w/o message (I didn't investigate this further)
Aside from this, rc seems to work O.K. under QNX RTP.
Stefan
next prev parent reply other threads:[~2001-11-01 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 16:18 Tim Goodwin
2001-11-01 17:35 ` Stefan Dalibor [this message]
2001-11-04 17:58 ` Scott Kenney
2001-11-01 16:20 erik quanstrom
2001-11-01 17:46 ` Scott Schwartz
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=20011101183503.A31677@caldera.de \
--to=dalibor@caldera.de \
--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).