From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6416 invoked by alias); 21 Oct 2009 15:40:17 -0000 Received: (qmail 6408 invoked by uid 22791); 21 Oct 2009 15:40:15 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-fx0-f223.google.com (HELO mail-fx0-f223.google.com) (209.85.220.223) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Oct 2009 15:40:09 +0000 Received: by fxm23 with SMTP id 23so8424095fxm.30 for ; Wed, 21 Oct 2009 08:40:07 -0700 (PDT) Received: by 10.204.150.81 with SMTP id x17mr6352036bkv.73.1256139606565; Wed, 21 Oct 2009 08:40:06 -0700 (PDT) Received: from localhost ([86.57.138.163]) by mx.google.com with ESMTPS id 15sm281825bwz.0.2009.10.21.08.40.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 21 Oct 2009 08:40:05 -0700 (PDT) Date: Wed, 21 Oct 2009 15:40:00 -0000 From: Sergei Gavrikov To: =?iso-8859-1?Q?=D8yvind?= Harboe Cc: eCos Disuss Message-ID: <20091021154001.GA4391@sg-laptop> Mail-Followup-To: =?iso-8859-1?Q?=D8yvind?= Harboe , eCos Disuss References: <20091021140357.GA18725@sg-ubuntu.local> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] extern __inline__ and optimisation problems X-SW-Source: 2009-10/txt/msg00141.txt.bz2 On Wed, Oct 21, 2009 at 05:16:38PM +0200, Øyvind Harboe wrote: > >> Also when I tried to upgrade from an older arm-elf to arm-eabi, I ran > >> into the same problem. > > > > I'm sorry, but, you do not provide enough of details to reproduce the > > issue with any toolchain. > > I know... I was hoping for some clues so I could > put together a complete reproducible example. > > I ran into this problem when trying to build an app using autotools > (openocd, in case you're interested). Hm, I do not expect that it's possible to mix native host archive (libopenocd.a) is built using host headers/glibc and eCos archives (libtarget.a, libextras.a) are built with eCos headers/libc even for Linux synthetic target together. GNU autotools (=configure) make compiler to use host's resources, eCos CT (ecosconfig) make compiler to use eCos resources (even for linux synthetic target). Sergei -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss