From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [New WinCE support] [patch 4/4] The bulk of the code.
Date: Thu, 29 Mar 2007 03:18:00 -0000 [thread overview]
Message-ID: <460AEFC7.6030707@portugalmail.pt> (raw)
In-Reply-To: <20070327192032.GJ28164@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Mon, Mar 19, 2007 at 01:16:15AM +0000, Pedro Alves wrote:
>
>> ChangeLog
>> * wince.c: Remove.
>> * wince-stub.h: Remove.
>> * wince-stub.c: Remove.
Humm, these files are still used by the current sh and mips WinCE
ports. As I
understand it, those ports are scheduled for removal. I'll post a separate
patch to remove them all.
> This is OK. Doesn't it deserve a NEWS entry?
>
Thanks a bunch!
I'll prepare a NEWS entry separately.
> I didn't go over the Windows-specific changes too closely; I trust you
> :-) I'll try not to break it too badly when working on the Linux ports.
>
>
Thanks for the trust :)
I've tried to make sure I didn't break Cygwin gdbserver in the process.
>> @@ -52,8 +52,14 @@ case "${target}" in
>> srv_linux_regsets=yes
>> srv_linux_thread_db=yes
>> ;;
>> + arm*-*-mingw32ce*) srv_regobj=reg-arm.o
>> + srv_tgtobj="win32-low.o win32-arm-low.o"
>> + srv_tgtobj="${srv_tgtobj} wincecompat.o"
>> + srv_mingw=yes
>> + srv_mingwce=yes
>> + ;;
>> i[34567]86-*-mingw*) srv_regobj=reg-i386.o
>> - srv_tgtobj="win32-low.o"
>> + srv_tgtobj="win32-low.o win32-i386-low.o"
>> srv_mingw=yes
>> ;;
>> ia64-*-linux*) srv_regobj=reg-ia64.o
>>
>
> Please put arm*-*-mingw32ce* up higher, near other ARM targets - the
> case statement is pretty much sorted.
>
>
Ok, I'll do that.
> Should you check arm-wince-pe here too, since you did in the directory
> above? Not that I expect a lot of native arm-wince-pe gdb :-)
I don't think so. arm-wince-pe is supposed (at least that is what I get
from the binutils archives
from the time Nick made the original binutils/gcc wince support, and
from current FSF
arm-wince-pe-gcc) to use MSFT's headers and libs, and as such will not
be able to build
gdbserver OOTB. Nevertheless, it should be possible to have an
arm-wince-pe-gdb
connect to a arm-wince-mingw32ce-gdbserver.
Cheers,
Pedro Alves
next prev parent reply other threads:[~2007-03-29 3:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070315235008.243411000@portugalmail.pt>
2007-03-16 2:07 ` [New WinCE support] [patch 1/4] : mv win32-i386-low.c win32-low.c Pedro Alves
2007-03-27 19:11 ` Daniel Jacobowitz
2007-03-16 2:09 ` [New WinCE support] [patch 3/4] : bfd config Pedro Alves
2007-03-16 2:09 ` [New WinCE support] [patch 2/4] : s/thread_info/win32_thread_info/g Pedro Alves
2007-03-27 19:12 ` Daniel Jacobowitz
2007-03-16 2:10 ` [New WinCE support] [patch 4/4] The bulk of the code Pedro Alves
2007-03-16 12:52 ` Eli Zaretskii
2007-03-16 15:03 ` pedro alves
2007-03-17 11:18 ` Eli Zaretskii
2007-03-17 11:35 ` Andreas Schwab
2007-03-19 1:53 ` Pedro Alves
2007-03-19 4:21 ` Eli Zaretskii
2007-03-19 12:34 ` Daniel Jacobowitz
2007-03-27 19:20 ` Daniel Jacobowitz
2007-03-29 3:18 ` Pedro Alves [this message]
2007-03-29 3:51 ` Pedro Alves
2007-03-30 11:56 ` Pierre Muller
2007-03-30 12:23 ` pedro alves
2007-03-30 20:35 ` 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=460AEFC7.6030707@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=eliz@gnu.org \
--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