From: Robert Schweikert <rjschwei@mindspring.com>
To: insight@sourceware.cygnus.com
Subject: parse error in tkInt.h
Date: Sat, 08 Jul 2000 03:50:00 -0000 [thread overview]
Message-ID: <396707EC.3CB9838D@mindspring.com> (raw)
I am trying to build insight on my RH 6.2 system using gcc 2.95 and
everything appears to be going OK until I get the following error:
gcc -c -g -O2 -I. -I./../generic -I./../bitmaps
-I/usr/local/insight-5.0/tcl/generic -I/usr/X11R6/include
-DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TIME_H=1
-DTIME_WITH_SYS_TIME=1 ./tkUnix3d.c
In file included from ../generic/tk3d.h:18,
from ./tkUnix3d.c:15:
../generic/tkInt.h:905: parse error before `_ANSI_ARGS_'
make[2]: *** [tkUnix3d.o] Error 1
make[2]: Leaving directory `/usr/local/insight-5.0/tk/unix'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/local/insight-5.0/tk'
make: *** [all-tk] Error 2
I looked at the header file but couldn't see anything wrong with line
905:
EXTERN void TkpSync _ANSI_ARGS_((Display *display));
Any help is appreciated.
Thanks,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
rjschwei@mindspring.com LINUX
reply other threads:[~2000-07-08 3:50 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=396707EC.3CB9838D@mindspring.com \
--to=rjschwei@mindspring.com \
--cc=insight@sourceware.cygnus.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).