From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27568 invoked by alias); 29 Jan 2009 14:15:16 -0000 Received: (qmail 27444 invoked by uid 22791); 29 Jan 2009 14:15:15 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Jan 2009 14:15:06 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id DE34F10A44; Thu, 29 Jan 2009 14:15:03 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 8FF25107FE; Thu, 29 Jan 2009 14:15:03 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LSXfb-0002uK-09; Thu, 29 Jan 2009 09:15:03 -0500 Date: Thu, 29 Jan 2009 14:15:00 -0000 From: Daniel Jacobowitz To: Jamie Lokier Cc: uClinux development list , gcc-help , binutils@sourceware.org Subject: Re: [uClinux-dev] why no-mmu cannot support binfmt_aout.c Message-ID: <20090129141502.GA11078@caradoc.them.org> Mail-Followup-To: Jamie Lokier , uClinux development list , gcc-help , binutils@sourceware.org References: <3a665c760901260851x4dfcc2beve282e8ba709e94e3@mail.gmail.com> <20090126235125.GC9296@shareable.org> <3a665c760901270902r582c60dfm2668a30c754aaf17@mail.gmail.com> <20090127183339.GA23412@shareable.org> <3a665c760901281016i562c8f6h36e77d72946bc704@mail.gmail.com> <4980EE0E.9040307@snapgear.com> <3a665c760901281600q19a5d0d2n4c4bb321cdbfba6c@mail.gmail.com> <4980F5C8.3040202@snapgear.com> <3a665c760901282207g5e203ef0rfbd51a1c2c9a80a9@mail.gmail.com> <20090129061215.GD19270@shareable.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090129061215.GD19270@shareable.org> User-Agent: Mutt/1.5.17 (2008-05-11) Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2009-01/txt/msg00297.txt.bz2 On Thu, Jan 29, 2009 at 06:12:15AM +0000, Jamie Lokier wrote: > I wouldn't be surprised if the Codesourcery tools (especially > pre-built libs) are targetting later ARM chips only, since people > using later ARM chips are probably paying Codesourcery for the work. Our tools support all (post-V4) ARM processors; I believe that we package libraries for all processors too nowadays. The defaults may be fairly modern, though - so as Jamie said, be sure to tell the tools what you want your code to run on! -- Daniel Jacobowitz CodeSourcery