From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb@sourceware.org
Subject: Re: Likely obsolete pieces of GDB
Date: Mon, 19 Feb 2007 01:25:00 -0000 [thread overview]
Message-ID: <45D82E95.1090401@portugalmail.pt> (raw)
In-Reply-To: <20070210235023.GA4959@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Sat, Feb 10, 2007 at 09:41:43PM +0000, Pedro Alves wrote:
>> I have the WinCE gdbserver port 99% ready for submission. There are just
>> a few other things I would like to solve first: is the target
>> name that I have been calling arm-wince-mingw32ce at cegcc.sourceforge.net
>> ok, or should I rename it?
>
> Didn't it used to be just arm-wince? Anyway, you'd have to ask the
> config-patches list.
>
It was called arm-wince-pe, but I saw some messages somewhere (I think in
the binutils archive) about how it should have been called arm-wince. The
original arm-wince(-pe) support was made using MSFT's SDK (headers and libs).
This new arm-wince-mingw32ce is a mingw32 derivative (*); We use winsup/mingw
and winsup/w32api adapted to wince. Plus, having mingw32 on the name eases
the porting by a whole bunch, since those "case ${host} in; case mingw*) ;; "
will, in most of the cases, be right for wince too. WinCE is *is* Windows
afterall, a quite broken one, but still...
Thanks for the config-patches list hint.
Cheers,
Pedro Alves
(*) - We never made a push to MinGW upstream, because first we needed to
know if the overlap would justify it, or if we should remain as a fork, and,
we didn't want to bother the busy MinGW folks with a half baked port.
next prev parent reply other threads:[~2007-02-18 10:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 20:59 Daniel Jacobowitz
2006-12-16 21:23 ` Christopher Faylor
2007-02-10 21:42 ` Pedro Alves
2007-02-10 23:50 ` Daniel Jacobowitz
2007-02-19 1:25 ` Pedro Alves [this message]
2006-12-17 1:24 ` John David Anglin
2006-12-17 11:46 ` Mark Kettenis
2007-01-01 16:34 ` Daniel Jacobowitz
2006-12-18 3:03 ` John David Anglin
2006-12-18 3:43 ` John David Anglin
2006-12-20 16:07 ` John David Anglin
2006-12-20 17:41 ` John David Anglin
2007-01-01 16:33 ` Daniel Jacobowitz
2007-01-01 16:47 ` John David Anglin
2007-01-01 17:10 ` Mark Kettenis
2007-01-01 17:20 ` John David Anglin
2006-12-17 1:36 ` Russell Shaw
2006-12-17 12:20 ` Mark Kettenis
2006-12-17 14:26 ` Stephen & Linda Smith
2006-12-17 15:37 ` Daniel Jacobowitz
2006-12-20 6:01 ` Joel Brobecker
2006-12-17 13:40 ` Joel Brobecker
2007-01-01 16:46 ` Daniel Jacobowitz
2007-01-01 16:58 ` Mark Kettenis
2007-01-03 23:55 ` Jim Blandy
2007-02-10 20:50 ` Daniel Jacobowitz
2007-02-12 17:35 ` Joel Brobecker
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=45D82E95.1090401@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=gdb@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