From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25498 invoked by alias); 4 May 2006 19:03:59 -0000 Received: (qmail 25406 invoked from network); 4 May 2006 19:03:44 -0000 Received: from unknown (195.23.133.213) by sourceware.org with QMTP; 4 May 2006 19:03:44 -0000 Received: (qmail 32673 invoked from network); 4 May 2006 19:03:42 -0000 Received: from unknown (HELO mailfrt08.isp.novis.pt) ([195.23.133.200]) (envelope-sender ) by mailrly03.isp.novis.pt with compressed SMTP; 4 May 2006 19:03:42 -0000 Received: (qmail 8275 invoked from network); 4 May 2006 19:03:39 -0000 Received: from unknown (HELO mamas-laptop) ([195.23.225.245]) (envelope-sender ) by mailfrt08.isp.novis.pt with SMTP; 4 May 2006 19:03:39 -0000 Received: from localhost ([127.0.0.1]) by mamas-laptop with esmtp (Exim 4.60) (envelope-from ) id IYR8XN-0007PS-2Z; Thu, 04 May 2006 20:03:23 +0100 Message-ID: <445A4FF9.2020903@portugalmail.pt> Date: Thu, 04 May 2006 19:03:00 -0000 From: Pedro Alves Reply-To: binutils@sourceware.org User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Daniel Jacobowitz CC: binutils@sourceware.org Subject: Re: Binutils on arm : pls advice me how to proceed References: <1146765307.4177.16.camel@dannypc> <20060504180348.GA5785@nevyn.them.org> In-Reply-To: <20060504180348.GA5785@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0618-2, 04-05-2006), Outbound message X-Antivirus-Status: Clean X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00090.txt.bz2 Daniel Jacobowitz wrote: > On Thu, May 04, 2006 at 07:55:07PM +0200, Danny Backx wrote: > >> Pedro Alves and I sent some message on the list that indicate where we >> think some of the problem areas are. >> >> Clearly, something must be wrong with those messages, as there appears >> to be little attention being payed to them. >> >> Can someone help me by telling me what I'm missing ? >> Am I sending the wrong information ? >> Am I talking to the wrong public ? >> Am I boring and should I just shut up ? :-) >> > > The maintainers are always busy; it sometimes takes a long time and a > couple of tries to get a response. Patience is very important. > I'm patient. :) > Fixes for WinCE don't normally get a lot of attention, because there's > a relatively small user base. > > Yes, I hope that the cegcc project can grow into "the" toolchain for wince development with gnu tools. When I started using arm-wince-* tools, the thing that almost kept me off, was the fact that the user base was so disperse. Some patches here and there, a few other places with prebuilt toolchains, but no central identity, like say, cygwin or mingw. Well, actually not quite true, there was/is GNUWINCE from Voxware, but at the time I thought it was a dead project. > FWIW, I skimmed some of the patches that have been sent; #ifdefs > are rarely OK. Although some are probably needed since the WinCE > loader is so different from typical ARM loaders, it's important to > minimize them, and to figure out (A) what the differences are supposed > to be, and (B) where the most effective place to implement the changes > is. I have to admit, I don't yet get the full picture of my own changes. I based my work on making the head version of binutils generate the same objects and images as the old (as in one year and a half ago) did. I am sure some (as in most) #ifdefs there are in the wrong place, but to my limited knowledge they were the best place I could find that would have minimum code changes. I would love to hear some directions of how to clean them up. > Another thing that helps to make your changes clear is new > testcases; if there had been enough testcases for the special WinCE > needs, it probably wouldn't have broken. > > Cheers, Pedro Alves