Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Manu" <manubee@wanadoo.fr>
To: "Mark Kettenis" <kettenis@chello.nl>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: Configure GDB for MinGW
Date: Tue, 25 May 2004 21:32:00 -0000	[thread overview]
Message-ID: <001001c442a1$768aeb00$4619fdc1@ftiy9yhq97> (raw)
In-Reply-To: <200405241736.i4OHapkM000351@elgar.kettenis.dyndns.org>

Mark Kettenis wrote:


> Thanks for your contribution.  I think it is small enough to be
> accepted without a copyright assignment, especially if you follow the
> advice below.  I'm not completely sure though.
>
> A few remarks and questions:
>
> 1. Please update the copyright year of new files or files that you
changed.
>
> 2. Please remove any empty variables in your .mh and .mt files.

Ok.

> 3. Is MH_CFLAGS=-D_POSIX in mingw32.mh really necessary?

I need to check that point.

> 4. Your nm-mingw32.h file seems to be a verbatim copy if nm-cygwin.h.
>    Please use nm-cygwin.h instead.
>
> 5. All your tm-mingw32.h file does in including tm-cygwin.h.  Actually
>    I think you can just use cygwin.mt instead of mingw32.mt.  I expect
>    that MinGW uses the same convention for returning structs as
>    Cygwin, so that will actually fix a few bugs.

Agreed.

> 6. Why is the line
>
>    #define getkey getch
>
>    in xm-mingw32.h needed?

getkey doesn't exist, but getch does.

> 7. Looks like ser-mingw32.c is doing nothing.  AFAICT it shouldn't be
>    necessary.

It would be for future use.

Thanks for your help, I'll submit a new diff file.

There's a few specific bugs with MinGW versions of GDB.
I hope to "./configure && make" from CVS sources soon, and then to find
out what goes wrong sometimes.

Manu.





      parent reply	other threads:[~2004-05-25 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 10:05 Manu
2004-05-24 17:36 ` Mark Kettenis
2004-05-24 21:01   ` Christopher Faylor
2004-05-25 21:32     ` Manu
2004-05-26  2:27       ` Christopher Faylor
2004-05-26 10:41         ` Eli Zaretskii
2004-05-25 21:32   ` Manu [this message]

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='001001c442a1$768aeb00$4619fdc1@ftiy9yhq97' \
    --to=manubee@wanadoo.fr \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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