Date: Mon, 14 Aug 2000 08:24:05 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: matt DOT l AT techie DOT com Message-Id: <7458-Mon14Aug2000082404+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b CC: djgpp AT delorie DOT com, djgpp AT delorie DOT com In-reply-to: <4.3.2.7.0.20000813160836.00acd790@mail.subdimension.com> (message from Matt Lewandowsky on Sun, 13 Aug 2000 16:09:15 -0700) Subject: Re: Uh oh. Another newbie. (Sorta...) References: <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20000813160836 DOT 00acd790 AT mail DOT subdimension DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Sun, 13 Aug 2000 16:09:15 -0700 > From: Matt Lewandowsky > > In file included from tparam.c:29: > d:/djgpp/include/string.h:52: parse error before `(' > d:/djgpp/include/string.h:52: parse error before `const' > make.exe: *** [tparam.o] Error 1 > lewellyn AT mattlap:/src/termcap-1.3*421$ > - ---END SNIPPET--- > > Just to make it easier to locate (even though it's a short file), line 52 > of strings.h reads: > > void * bcopy(const void *_a, void *_b, size_t _len); I'm guessing that some other include file or tparam.c itself #define'd bcopy to something that caused this parse error. You need to grep all the termcap sources for "bcopy". Btw, the above prototype is in error: it needs to say "void bcopy...", not "void * bcopy...". But that usually won't cause any compilation problems, unless some #define causes it. > Note that I actually gave -v output this time... That's a very good habit ;-) > I'm really not sure what strings.h this line should be You mean, string.h, not strings.h, yes? > I've been pounding on this for a couple days now, but to no avail. Is there > an alternate set of headers available that work that may solve this > problem? (Please don't laugh...) Perhaps I'm just trying to do the > impossible for DOS? No, I'd guess that there's some bug in termcap (I don't think it is maintained actively).