From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] [3/4] Mingw64 gdbserver support
Date: Mon, 19 Apr 2010 23:41:00 -0000 [thread overview]
Message-ID: <001e01cae019$df74abd0$9e5e0370$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <201004200030.23956.pedro@codesourcery.com>
> -----Message d'origine-----
> De : Pedro Alves [mailto:pedro@codesourcery.com]
> Envoyé : Tuesday, April 20, 2010 1:30 AM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFA] [3/4] Mingw64 gdbserver support
>
> On Monday 19 April 2010 23:58:55, Pierre Muller wrote:
> > gdbserver/configure.srv part of the patch.
> >
> >
> >
> > Pierre Muller
> > Pascal language support maintainer for GDB
> >
> > 2010-04-19 Pierre Muller <muller@ics.u-strasbg.fr>
> >
> > * configure.srv (x86_64-*-mingw*): New configuration for
> Windows
> > 64-bit executables.
>
> Weren't you going to s/x86_64-w64-mingw/x86_64-*-mingw/ ? The
> ChangeLog
> mentions the latter, but the patch does the former.
Whooops, sorry for this.
> > Set srv_mingw64 variable to `yes'.
>
> Why is this needed? I don't see anywhere in the patch series
> using it. Wasn't this needed in the older version to have configure.ac
> link with -lws2_32 for this config only, but it's not needed anymore?
You are perfectly right.
Still simpler!
2010-04-19 Pierre Muller <muller@ics.u-strasbg.fr>
* configure.srv (x86_64-*-mingw*): New configuration for Windows
64-bit executables.
Index: gdbserver/configure.srv
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/configure.srv,v
retrieving revision 1.54
diff -u -p -r1.54 configure.srv
--- gdbserver/configure.srv 19 Apr 2010 14:08:05 -0000 1.54
+++ gdbserver/configure.srv 19 Apr 2010 22:42:53 -0000
@@ -231,6 +231,12 @@ case "${target}" in
srv_linux_regsets=yes
srv_linux_thread_db=yes
;;
+ x86_64-*-mingw*) srv_regobj="$srv_amd64_regobj"
+ srv_tgtobj="i386-low.o i387-fp.o win32-low.o
win32-i386-low.o"
+ srv_xmlfiles="$srv_i386_xmlfiles
$srv_amd64_xmlfiles"
+ srv_mingw=yes
+ ;;
+
xscale*-*-linux*) srv_regobj=reg-arm.o
srv_tgtobj="linux-low.o linux-arm-low.o"
srv_linux_usrregs=yes
next prev parent reply other threads:[~2010-04-19 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 22:58 Pierre Muller
2010-04-19 23:30 ` Pedro Alves
2010-04-19 23:41 ` Pierre Muller [this message]
2010-04-19 23:56 ` Pedro Alves
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='001e01cae019$df74abd0$9e5e0370$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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