[ECOS] extern __inline__ and optimisation problems

Øyvind Harboe oyvind.harboe@zylin.com
Wed Oct 21 16:50:00 GMT 2009


On Wed, Oct 21, 2009 at 6:15 PM, Sergei Gavrikov
<sergei.gavrikov@gmail.com> wrote:
> On Wed, Oct 21, 2009 at 06:04:48PM +0200, Ųyvind Harboe wrote:
>> > 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.
>>
>> I'm not (willingly) mixing host and eCos stuff. I'm crossbuilding
>> using autotools to eCos binaries.
>>
>> This works fine for my arm-elf target, but something goes
>> haywire with arm-eabi and gcc. I suspect that it might be
>> a gcc 3 vs. gcc 4 problem. My suspicion is that I've got one
>> option too many or too little...
>
> Search: gcc 4 extern inline
> http://gcc.gnu.org/gcc-4.3/porting_to.html
>
> May be that's it.

It almost certainly is... Thanks for the tip!

Does this really mean that *all* those places in eCos have to
be touched to become compatible with the -std=c99 or -std=gnu99
options?

Ouch.

-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



More information about the Ecos-discuss mailing list