Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: Pierre Muller <muller@cerbere.u-strasbg.fr>,
	gdb@sources.redhat.com, Mark Kettenis <kettenis@science.uva.nl>
Subject: Re: [RFC/RFA] fix  cygwin GDB "long long" return value error
Date: Wed, 10 Oct 2001 19:50:00 -0000	[thread overview]
Message-ID: <3BC5085E.7A398D76@apple.com> (raw)
In-Reply-To: <20011010221023.B13834@redhat.com>

Christopher Faylor wrote:
> 
> On Fri, Oct 05, 2001 at 12:00:09PM +0200, Pierre Muller wrote:
> >Could someone, (Christopher ?) explains us why tm-cygwin.h includes
> >tm-i386v.h when as Mark Kettenis said, Cygwin is not derived from
> >System V ?
> 
> I am sorry but I really can't explain why tm-cygwin.h includes
> tm-i386v.h.  I believe that predates my maintainership.

Probably because Windows uses COFF, as does SVR3, so in a very loose
sense, Cygwin does have an ancestral relationship with SVR3.
Ironically, it doesn't look like there are any actual vestiges of
COFFness left in tm-i386v.h

Stan


  reply	other threads:[~2001-10-10 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pierre>
     [not found] ` <Muller's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <Thu,>
     [not found]         ` <04>
     [not found]           ` <Oct>
     [not found]             ` <2001>
     [not found]               ` <01:24:30>
     [not found]                 ` <+0200>
2001-10-03 16:17                   ` [RFC] " Pierre Muller
2001-10-04 12:08                     ` Mark Kettenis
2001-10-05  3:12                       ` [RFC/RFA] fix " Pierre Muller
2001-10-10 19:09                         ` Christopher Faylor
2001-10-10 19:50                           ` Stan Shebs [this message]
2001-10-11 21:33                           ` 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=3BC5085E.7A398D76@apple.com \
    --to=shebs@apple.com \
    --cc=cgf@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@science.uva.nl \
    --cc=muller@cerbere.u-strasbg.fr \
    /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