Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com List-Unsubscribe: List-Archive: List-Help: , Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199907292131.QAA18618@pluto.xraylith.wisc.edu> To: "Josh Baudhuin" cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: gcc build error--configuration problem? In-Reply-To: Your message of "Thu, 29 Jul 1999 14:20:32 PDT." Date: Thu, 29 Jul 1999 16:31:44 -0500 From: Mumit Khan "Josh Baudhuin" writes: > > I just installed the 'full' binary release of 20.1. Then I tried to build > cvs-1.10 using the tar from the net. > > The 'configure' script seemed to run w/o a hitch, but when I build, I get a > compile error when it comes to src/rcs.c: [ ... ] > gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O -c rcs.c > rcs.c: In function `apply_rcs_changes': > rcs.c:6994: parse error before `(' > make[1]: *** [rcs.o] Error 1 > make: *** [all] Error 1 > [ ... ] > > Seems like there must be a macro in there for ADD or DELETE. Is the > configuration wrong? Do I need to do more to set up the build environment > than the simple install of full.exe? [Doesn't seem to be a CDK install > anymore.] > The windows32api headers define a DELETE macro, which is obviously not what RCS expects. You may need to insert a #undef DELETE after the appropriate to nullify the windows one and use RCS one. Damn these namespace polluting macros in system headers. My preference of course is to change the RCS macros/enums to use RCS_ prefix and be done with it. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com