bug-rcs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RCS will not compile om CentOS 8


From: Knight, Dave
Subject: Re: RCS will not compile om CentOS 8
Date: Mon, 28 Sep 2020 18:31:18 -0400

Thanks for the patch!

This patch fixes the compile problem, but when I run "make check", 
test t810 fails (this may be unrelated to the fix):

...
PASS: t803
PASS: t804
PASS: t805
FAIL: t810
PASS: t900
PASS: t999
================================
1 of 51 tests failed
Please report to bug-rcs@gnu.org
================================
make[2]: *** [Makefile:1502: check-TESTS] Error 1
make[2]: Leaving directory '/home/dmk/RCS/rcs-5.9.4-fix/rcs-5.9.4/tests'
make[1]: *** [Makefile:1626: check-am] Error 2
make[1]: Leaving directory '/home/dmk/RCS/rcs-5.9.4-fix/rcs-5.9.4/tests'
make: *** [Makefile:1392: check-recursive] Error 1
dmk@del1:~/RCS/rcs-5.9.4-fix/rcs-5.9.4$

Perhaps the code for test t810 is informative:

# t810 --- ci -l -d -T FILE

<(C) boilerplate>

. $srcdir/common
split_std_out_err no
. $srcdir/common-d

##
# Check that ‘ci -l -d -T FILE’ does not set
# the mtime of FILE,v to the epoch.
# This test derives from a 5.8 regression (and bugfix).
##

must 'echo new line >> $w'
must 'ci -mm -l -d -T $w'
test $w -nt $v && problem "$w newer than $v"

exit 0

# t810 ends here

That said, I doubt that this failure will impact use of this build with /BriefCase as the problem for which it tests 
seems not to be among the things that /BriefCase does with the RCS ci command.

Nevertheless, I hope this email is helpful.

Dave Knight
Applied-cs-inc.com (0wner) and author of the 
/BriefCase Revision Control and Release Management toolkit 
which uses the RCS engine.

--

In your time of need, may your piece be with you!

The trouble with many of today's college graduates is not that they're
ignorant, it's that they've been taught so much that just isn't so!

                                                      (with apologies to Ronald Reagan).



On Mon, Sep 28, 2020 at 5:33 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
On 9/28/20 12:51 PM, Bill P wrote:

> b-anchor.c:99:1: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before '{' token
>
> {

This is due RCS 5.9.4's misuse of _Noreturn. The attached patch should work
around the bug (but is good for GCC-compatible compilers only; something fancier
is needed for other compilers).

Looks like it's time for a new RCS release, if only to fix this porting glitch.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]