Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Danny Smith <danny_r_smith_2001@yahoo.co.nz>
Cc: GDB Discussion <gdb@sources.redhat.com>,
	mingw-users@lists.sourceforge.net
Subject: Re: [Mingw-users] Re: _WIN32?
Date: Mon, 30 Apr 2001 17:03:00 -0000	[thread overview]
Message-ID: <20010430200440.B29804@redhat.com> (raw)
In-Reply-To: <20010430231939.6198.qmail@web6402.mail.yahoo.com>

On Tue, May 01, 2001 at 09:19:39AM +1000, Danny Smith wrote:
>
>--- Christopher Faylor <cgf@redhat.com> wrote: > On Mon, Apr 30, 2001 at
>01:05:17PM -0400, Andrew Cagney wrote:
>> >Christopher Faylor wrote:
>> >
>> >>         _WIN32          Pure WIN32 support 'gcc -mno-cygwin' --
>> >>                         don't know if it even builds.  _WIN32 is
>> >>                         now no longer defined by gcc.
>> >
>> >So, can I delete this one? :-)
>> 
>> I don't know.  Someone used to maintain a non-cygwin Windows version of
>> gdb.  I don't know if it even builds, like I said.  I'm not even sure
>> how to configure it.
>> 
>> Perhaps the people at mingw-users@lists.sourceforge.net know the answer
>> to this?  I've Cc'ed them.
>
>The last non-cygwin windows version of gdb that I know of is 4.18 which Mumit
>made available here: 
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/ports
>
>The diff file for that port is dated May 1999.
>
>I have just started work on gdb 5.0 for mingw. I have not gotten far, mainly
>because of lack of time.  Has anyone else made progress.

If you are at least considering this, then it sounds like the _WIN32 conditionals
in gdb sources should not be removed.

I assume that they will be required if you build a no-cygwin version of gdb,
correct?

cgf


  reply	other threads:[~2001-04-30 17:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 14:50 _WIN32? Andrew Cagney
2001-04-17 14:59 ` _WIN32? Mo DeJong
2001-04-17 15:06 ` _WIN32? Christopher Faylor
2001-04-30 10:05   ` _WIN32? Andrew Cagney
2001-04-30 10:15     ` _WIN32? Christopher Faylor
2001-04-30 16:19       ` [Mingw-users] _WIN32? Danny Smith
2001-04-30 17:03         ` Christopher Faylor [this message]
2001-04-30 17:29           ` Danny Smith
2001-05-01  7:03           ` Kai Ruottu
2001-05-01  7:44             ` Christopher Faylor
2001-04-30 18:00       ` _WIN32? Andrew Cagney
2001-04-17 17:45 ` _WIN32? DJ Delorie
2001-04-18  2:17   ` _WIN32? Eli Zaretskii
     [not found] <200105010009.RAA12115@tully.CS.Berkeley.EDU>
2001-05-03  1:24 ` [Mingw-users] _WIN32? Paul Hilfinger
2001-05-03 13:41   ` Andrew Cagney
2001-05-03 14:15     ` Danny Smith
2001-05-03 15:24       ` Andrew Cagney
2001-05-03 15:54         ` Christopher Faylor
2001-05-03 16:11           ` Andrew Cagney
2001-05-04  2:17             ` Eli Zaretskii
2001-05-04  2:19         ` Eli Zaretskii
2001-05-04  8:45           ` Christopher Faylor
2001-05-04 10:18             ` Eli Zaretskii
2001-05-04 12:04               ` Christopher Faylor
2001-05-07  9:08         ` Eli Zaretskii
2001-05-03 23:58     ` Paul Hilfinger
2001-05-04  9:04       ` Andrew Cagney
2001-05-04  0:20     ` Eli Zaretskii
2001-05-05 15:57 Danny Smith
2001-05-05 18:54 ` Christopher Faylor
2001-05-05 23:03   ` Eli Zaretskii
2001-05-05 23:02 ` Eli Zaretskii
2001-05-06  1:52   ` Danny Smith

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=20010430200440.B29804@redhat.com \
    --to=cgf@redhat.com \
    --cc=danny_r_smith_2001@yahoo.co.nz \
    --cc=gdb@sources.redhat.com \
    --cc=mingw-users@lists.sourceforge.net \
    /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