From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25612 invoked by alias); 13 Oct 2007 19:09:14 -0000 Received: (qmail 25594 invoked by uid 22791); 13 Oct 2007 19:09:12 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (213.8.233.22) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 13 Oct 2007 19:09:09 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-249-214.inter.net.il [80.230.249.214]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id IAF54957 (AUTH halo1); Sat, 13 Oct 2007 21:06:25 +0200 (IST) Date: Sat, 13 Oct 2007 19:09:00 -0000 Message-Id: From: Eli Zaretskii To: Pedro Alves CC: brobecker@adacore.com, Kai.Tietz@onevision.com, gdb@sourceware.org In-reply-to: <4711021C.8010805@portugalmail.pt> (message from Pedro Alves on Sat, 13 Oct 2007 18:36:28 +0100) Subject: Re: Support of gdb for Windows 64 native systems Reply-to: Eli Zaretskii References: <20071011145549.GA19918@caradoc.them.org> <20071012161132.GE4044@adacore.com> <20071012174218.GH4044@adacore.com> <20071012222842.GD21800@adacore.com> <20071013024116.GB29152@adacore.com> <20071013154715.GE29152@adacore.com> <4711021C.8010805@portugalmail.pt> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-10/txt/msg00097.txt.bz2 > Date: Sat, 13 Oct 2007 18:36:28 +0100 > From: Pedro Alves > CC: Eli Zaretskii , 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.