Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] windows-nat.c: Cygwin: Port to Cygwin 1.7
Date: Sun, 28 Feb 2010 17:09:00 -0000	[thread overview]
Message-ID: <20100228170908.GJ5683@calimero.vinschen.de> (raw)
In-Reply-To: <000901cab897$02f00fa0$08d02ee0$@muller@ics-cnrs.unistra.fr>

On Feb 28 17:56, Pierre Muller wrote:
>   Is your patch cygwin 1.7 specific?
>   Are the new path conversion routines 
> also available for older cygwin version?
> 
>   Can we still compile GDB with the cygwin 1.5 
> after your patch is committed?
> 
>   There reason I am asking is that
> with release 1.7,
> cygwin dropped support for pre-Windows 2000
> windows releases ...

No, it doesn't.  It only drops support for the very crufty, very
outdate, and very buggy 95, 98 and Me versions of Windows.
Windows NT 4 is still supported.

>   Would it be possible to keep pre-1.7 support
> by adding using special preprocessor defines?

Not from my POV.  Cygwin 1.5 is deprecated and you can easily use
an older GDB with it.  However, it's cgf's call.


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat


  reply	other threads:[~2010-02-28 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28 15:09 Corinna Vinschen
2010-02-28 16:56 ` Pierre Muller
2010-02-28 17:09   ` Corinna Vinschen [this message]
2010-02-28 17:08 ` Eli Zaretskii
2010-02-28 17:18   ` Corinna Vinschen
2010-02-28 17:49     ` Eli Zaretskii
2010-02-28 18:01       ` Corinna Vinschen
2010-02-28 18:56         ` Eli Zaretskii
2010-02-28 19:24           ` Corinna Vinschen
2010-02-28 22:30 ` Christopher Faylor
2010-03-01  9:10   ` Corinna Vinschen
2010-03-01 10:04 Roland Schwingel
2010-03-01 15:23 ` Christopher Faylor

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=20100228170908.GJ5683@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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