From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] Updated: rcs-5.9.3
Date: Sun, 05 Oct 2014 09:33:00 -0000 [thread overview]
Message-ID: <announce.874mvihoy9.fsf@Rainer.invalid> (raw)
This release brings RCS to version 5.9.3 for both architectures. A
slightly modified version of the patch for the RCS work file corruption
problem is now included in the upstream sources along with a test, so no
Cygwin specific patches need to be applied.
--8<---------------cut here---------------start------------->8---
NEWS for 5.9.3 (2014-09-17):
- compatibility w/ RCS 2.x file format dropped
This was presaged w/ RCS 5.9.0 (released 2013-05-06), below.
Effectively, the configure script no longer supports option
‘--enable-compat2’, and RCS programs will fail, reporting a
syntax error, if given a comma-v file in 2.x format.
- bug fixes
- crash on co/ci without changes on a branch
RCS 5.8 (released 2011-08-30) introduced a bug whereby a ci
without changes (i.e., reversion) on a branch would crash,
leaving a temporary files and corrupted comma-v file as well.
This regression is now fixed. See tests/t804, and also:
http://lists.gnu.org/archive/html/bug-rcs/2014-01/msg00000.html
- file corruption using stdio under Cygwin, Darwin
RCS 5.8 (released 2011-08-30) introduced a bug when using stdio
(e.g., with env var ‘RCS_MEM_LIMIT’ set to "0") under Cygwin
whereby ci with a sufficiently large working file would silently
write a truncated comma-v file. See tests/t805, and also:
http://lists.gnu.org/archive/html/bug-rcs/2014-06/msg00000.html
(Although the bug was initially discovered under Cygwin, the
Hydra project reported the same problem for Darwin.)
- portability fixes
- don't recurse on ‘main’
This is for the sake of Cygwin "make check". See:
http://lists.gnu.org/archive/html/bug-rcs/2014-08/msg00015.html
- avoid C99 VLA elems in func decl, sometimes
This is for the sake of Solaris 10 + GCC 3.4.3. See:
http://lists.gnu.org/archive/html/bug-rcs/2014-08/msg00002.html
- new diff/diff3 cross-compilation support
The configure script now assigns "optimistic defaults" to some
diff/diff3-related vars when cross-compiling and invoked with
vars ‘DIFF’ and ‘DIFF3’. See README.
- maintenance tools updated
- automake (GNU automake) 1.14.1
- gnulib-tool (GNU gnulib 2014-09-16 19:26:48) 0.1.222-aa0c2
--8<---------------cut here---------------end--------------->8---
Regards
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2014-10-05 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=announce.874mvihoy9.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).