Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Wed, 7 Nov 2001 18:11:03 +0300 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <160456152372.20011107181103@logos-m.ru> To: Christopher Faylor Subject: Re: Want to be a gcc/binutils maintainer? In-Reply-To: <20011107002202.A11903@redhat.com> References: <20010908230405 DOT A17395 AT redhat DOT com> <20011107002202 DOT A11903 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Wednesday, 07 November, 2001 Christopher Faylor cgf AT redhat DOT com wrote: CF> I got a couple of nibbles about this before. CF> Anyone interested in this exciting and challenging responsibility? well, i'm interested. that doesn't mean i'm sure i'm capable, though :) i'm now in process of debugging and fixing regressions in -3_0 and -current branches, but, i still haven't looked at -mno-cygwin and dll-specific stuff. i wonder if we can create a branch in gcc cvs tree to make cygwin-specific gcc development process a bit more "public"? for instance, this patch 2001-11-07 Egor Duda * config/i386/cygwin.h: Strip leading '*' from name, if any. Index: gcc/config/i386/cygwin.h =================================================================== RCS file: /usr/home/deo/cvsroot/cvs-mirrors/sourceware/gcc/gcc/config/i386/cygwin.h,v retrieving revision 1.33.2.15 diff -u -p -2 -r1.33.2.15 cygwin.h --- gcc/config/i386/cygwin.h 2001/10/26 04:25:00 1.33.2.15 +++ gcc/config/i386/cygwin.h 2001/11/06 21:10:16 @@ -356,4 +356,5 @@ do { \ const char *_p; \ const char *_name = I386_PE_STRIP_ENCODING (SYMBOL_NAME); \ + if (*_name == '*') _name++; \ for (_p = _name; *_p && *_p != '@'; ++_p) \ ; \ fixes one of testsuite regressions in 3_0 and make it possible to build -current natively. I don't know, though, if it's correct way to deal with this particular problem. CF> On Sat, Sep 08, 2001 at 11:04:05PM -0400, Christopher Faylor wrote: >>I picked up gcc and binutils maintainership because the previous people >>who had been doing it sort of went silent. >> >>Maintaining these packages is not something that I want to do, however. >> >>Is anyone else interested in doing this? Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19