From: Mo DeJong <mdejong@cygnus.com>
To: gdb@sources.redhat.com
Subject: Re: Problems building build-gdb20001125-1 on winnt (cygwin)
Date: Thu, 05 Apr 2001 23:15:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010405231133.29851N@cse.cygnus.com> (raw)
In-Reply-To: <F108vAauNjVuMhvqgSt000001b3@hotmail.com>
On Tue, 3 Apr 2001, Mack Lobell wrote:
> In regards to my last question (Ref.
> F13626yJKs8TAGUjGnA0000804b@hotmail.com ). I downloaded two versions from the
> GDB webpage, GDB 5.0 and GDB+Insigth5.0. The pure GDB 5.0 (without Insight)
> compiles and works under cygwin, no problems. When i compile Insight i get
> the same problem as with build-gdb20001125-1.
>
> The binary version of build-gdb20001125-1 works, and the help says version
> 5.0, so someone must have been able to build?
>
> Anyway, the problem lies in the following code:
> #ifndef VOID
> #define VOID void
> typedef char CHAR;
> typedef short SHORT;
> typedef long LONG;
> #endif
> typedef CHAR CCHAR;
> typedef unsigned char UCHAR,*PUCHAR;
> typedef unsigned short USHORT,*PUSHORT;
> typedef unsigned long ULONG,*PULONG;
> typedef char *PSZ;
You know, I ran into this same problem. The reason you
get this error with Insight is because it shows up in
the Tcl/Tk code, which is not part of regular gdb.
I have not had enough time to look into it (perhaps
next week), but I did find that the mingw version
of gcc is able to compile the code. I am
not sure if that helps, I just thought you
might like to know.
Mo DeJong
Red Hat Inc
next prev parent reply other threads:[~2001-04-05 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 9:57 Mack Lobell
2001-04-03 12:38 ` Christopher Faylor
2001-04-05 23:15 ` Mo DeJong [this message]
2001-04-06 7:15 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2001-04-02 8:17 Mack Lobell
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=Pine.SOL.3.91.1010405231133.29851N@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=gdb@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