RCS will not compile om CentOS 8
"Bill P" <[email protected]> Mon, 28 Sep 2020 14:51:16 -0500
| Newsgroups | gmane.comp.version-control.rcs.bugs |
|---|---|
| Message-ID | <[email protected]> |
This is a multipart message in MIME format.
------=_NextPart_000_0001_01D695A6.D18D5AA0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hi,
I am contracting for a company who has some customers that still use RCS for
their revision management. Some of those customers wish to move to migrate
to CentOS 7 or 8. When attempting to compile against CentOS 8 the following
error occurs:
b-anchor.c:99:1: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '{' token
{
^
b-anchor.c:121:1: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '{' token
{
^
b-anchor.c:133:1: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '{' token
{
^
b-anchor.c:145:1: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '{' token
{
^
b-anchor.c:166:1: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '{' token
{
^
In file included from b-anchor.c:21:
base.h:757:6: error: old-style parameter declarations in prototyped function
definition
void unexpected_EOF (void)
^~~~~~~~~~~~~~
b-anchor.c:180: error: expected '{' at end of input
/* b-anchor.c ends here */
I know that RCS is basically a dead revision control program, and we are
working to move them to Git as their revision control system, however they
have years of code invested in RCS that they do not wish to loose since
CentOS 6 is now End of Life. So any help would be appreciated.
Thank You
Bill P
"You don't get a participation trophy for life; you take what you get and
play your best hand. It's been that way since forever."
William Shatner
------=_NextPart_000_0001_01D695A6.D18D5AA0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><p class=3DMsoNormal>I am =
contracting for a company who has some customers that still use RCS for =
their revision management. Some of those customers wish to move to =
migrate to CentOS 7 or 8. When attempting to compile against CentOS 8 =
the following error occurs:<o:p></o:p></p><p =
class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>b-anchor.c:99:1: error: expected ‘=3D’, =
‘,’, ‘;’, ‘asm’ or =
‘__attribute__’ before ‘{’ =
token<o:p></o:p></p><p class=3DMsoNormal> {<o:p></o:p></p><p =
class=3DMsoNormal> ^<o:p></o:p></p><p =
class=3DMsoNormal>b-anchor.c:121:1: error: expected ‘=3D’, =
‘,’, ‘;’, ‘asm’ or =
‘__attribute__’ before ‘{’ =
token<o:p></o:p></p><p class=3DMsoNormal> {<o:p></o:p></p><p =
class=3DMsoNormal> ^<o:p></o:p></p><p =
class=3DMsoNormal>b-anchor.c:133:1: error: expected ‘=3D’, =
‘,’, ‘;’, ‘asm’ or =
‘__attribute__’ before ‘{’ =
token<o:p></o:p></p><p class=3DMsoNormal> {<o:p></o:p></p><p =
class=3DMsoNormal> ^<o:p></o:p></p><p =
class=3DMsoNormal>b-anchor.c:145:1: error: expected ‘=3D’, =
‘,’, ‘;’, ‘asm’ or =
‘__attribute__’ before ‘{’ =
token<o:p></o:p></p><p class=3DMsoNormal> {<o:p></o:p></p><p =
class=3DMsoNormal> ^<o:p></o:p></p><p =
class=3DMsoNormal>b-anchor.c:166:1: error: expected ‘=3D’, =
‘,’, ‘;’, ‘asm’ or =
‘__attribute__’ before ‘{’ =
token<o:p></o:p></p><p class=3DMsoNormal> {<o:p></o:p></p><p =
class=3DMsoNormal> ^<o:p></o:p></p><p class=3DMsoNormal>In file included =
from b-anchor.c:21:<o:p></o:p></p><p class=3DMsoNormal>base.h:757:6: =
error: old-style parameter declarations in prototyped function =
definition<o:p></o:p></p><p class=3DMsoNormal> void unexpected_EOF =
(void)<o:p></o:p></p><p class=3DMsoNormal> =
^~~~~~~~~~~~~~<o:p></o:p></p><p class=3DMsoNormal>b-anchor.c:180: error: =
expected ‘{’ at end of input<o:p></o:p></p><p =
class=3DMsoNormal> /* b-anchor.c ends here */<o:p></o:p></p><p =
class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>I know that =
RCS is basically a dead revision control program, and we are working to =
move them to Git as their revision control system, however they have =
years of code invested in RCS that they do not wish to loose since =
CentOS 6 is now End of Life. So any help would be =
appreciated.<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>Thank You <o:p></o:p></p><p class=3DMsoNormal>Bill =
P<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>"You don’t get a participation trophy for =
life; you take what you get and play your best hand. It’s been =
that way since forever.”<o:p></o:p></p><p =
class=3DMsoNormal>William Shatner<o:p></o:p></p><p =
class=3DMsoNormal><o:p> </o:p></p></div></body></html>
------=_NextPart_000_0001_01D695A6.D18D5AA0--