Re: Support of gdb for Windows 64 native systems

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 13 Oct 2007 18:36:28 +0100
> From: Pedro Alves <pedro_alves@portugalmail.pt>
> CC: Eli Zaretskii <eliz@gnu.org>,  Kai.Tietz@onevision.com, 
>  gdb@sourceware.org
> 
> Joel Brobecker wrote:
> 
> > I think at this point that the next thing to do is to review carefully
> > the patch, and evaluate what is needed and what isn't anymore. Then
> > we can tackle the issue of copyright assignement, and then finally
> > submit/discuss a new patch.
> > 
> 
> That is IMHO, the wrong way to do it.  The copyright assignment
> should be resolved first, before everyone looks into the patches.
> Otherwise, it taints whoever looks at the thread, and inhibits that
> someone from redoing it from scratch, if the copyright issues end up
> unresolved doesn't it?

If someone describes the changes, and someone else codes them, there's
no need to resolve the copyright issues.  Copyright only deals with
verbatim copying of the code; ideas cannot be copyrighted.

However, I agree that having everyone look at the patches is not a
very good idea, since it will make it harder not to copy code.

> I propose goind the other way around.  Start by adding the needed configury
> bits needed, a mingw.mt file, and disabling the cygwin specific bits in
> win32-nat.c around #ifdef __CYGWIN__ blocks.  I'd like to keep the
> changes mostly in sync with gdbserver/win32-low.c too, but that shouldn't
> be a priority.  We can then peacewise enhance the mingw port and bring
> its features up.

We don't need to go that slow.