public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: bobwirka@yahoo.com
To: insight-gnats@sourceware.cygnus.com
Subject: insight/86: Make fails at tclEnv.c; CCHAR unrecognized
Date: Sun, 01 Apr 2001 11:43:00 -0000	[thread overview]
Message-ID: <20010401183639.2344.qmail@sourceware.cygnus.com> (raw)

>Number:         86
>Category:       insight
>Synopsis:       Make fails at tclEnv.c; CCHAR unrecognized
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 01 11:43:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Bob Wirka
>Release:        Insight 5.0
>Organization:
>Environment:
Windows 2000 Pro and Win98, installing for eCos system
in Cygwin for i386-elf target.
>Description:
Make fails while compiling 'tclEnv.c' in tcl part of build:

(From make.out)
In file included from /usr/include/w32api/windef.h:143,
                 from /usr/include/w32api/windows.h:96,
                 from /src/gdb/insight-5.0/tcl/cygwin/../generic/tclEnv.c:750:
/usr/include/w32api/winnt.h:48: parse error before `CCHAR'

The offending line in 'winnt.h' is:

typedef CHAR CCHAR;

More errors occur, but seem basically caused by CHAR, USHORT,
and some other items not being defined.

I've followed the install instructions per the Red Hat website.

Both /tmp and /src are mounted in 'binary' mode.

Both 'binutils' and 'gcc' have built ok. Have built 'gdb' for
i386-elf target; it works.

Has anyone else seen this? Any suggestions?

Thank you.
>How-To-Repeat:
Just configure and make. Fails every time on both Win98 and
Windows 2000 Pro.
>Fix:
None yet?
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-04-01 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01 11:43 bobwirka [this message]
2002-01-04 14:17 kseitz

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=20010401183639.2344.qmail@sourceware.cygnus.com \
    --to=bobwirka@yahoo.com \
    --cc=insight-gnats@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).