From: Oleg Ostrozhansky <oleg@olegos.com>
To: insight@sources.redhat.com
Subject: Re: make problem
Date: Wed, 08 Oct 2003 21:05:00 -0000 [thread overview]
Message-ID: <20031008210537.GA10946@panix.com> (raw)
In-Reply-To: <1065603011.d1c52e486be23@webmail.tugraz.at>
On Wed, Oct 08, 2003 at 10:50:11AM +0200, hoer@sbox.tugraz.at wrote:
> Hi!
> I'm working on a Windows 2000 machine with Cygwin. I want to configure
> insight5.3 for m68k. Configuring works, but the make prozess stops and I don't
> know, what I should do.
> I've also tried to do the toolchain first from Martin Hunt to use the Tcl/Tk
> 8.0.3. but no way.
>
>
> Tanks for any info!
>
>
> Here is my ouput:
...
> ../generic/tclCmdAH.c:670: error: parse error before numeric constant
The problem is that in that file (tcl/generic/tclCmdAH.c) there is an enum
with member FILE_EXISTS. But that symbol is also used in
/usr/include/w32api/winnt.h and /usr/include/w32api/ddk/winddk.h under
cygwin. I just renamed it in the two places it's used in tclCmdAH.c,
and the build completed.
Oleg
next prev parent reply other threads:[~2003-10-08 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 8:50 hoer
2003-10-08 9:39 ` Paul Whitfield
2003-10-08 21:05 ` Oleg Ostrozhansky [this message]
2003-10-09 1:03 ` Keith Seitz
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=20031008210537.GA10946@panix.com \
--to=oleg@olegos.com \
--cc=insight@sources.redhat.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).