[U-Boot] CONFIG_API, EABI and raise()

Rafal Jaworowski
2009-07-16T09:29:55Z

Hi Stefan,

On 2009-07-16, at 10:46, Stefan Roese wrote:

> On Thursday 16 July 2009 10:37:34 Rafal Jaworowski wrote:
>> On 2009-07-15, at 18:09, Mike Frysinger wrote:
>>> On Wednesday 15 July 2009 11:15:46 Rafal Jaworowski wrote:
>>>> On 2009-07-15, at 16:58, Mike Frysinger wrote:
>>>>> On Tuesday 14 July 2009 09:47:26 Piotr Zi?cik wrote:
>>>>>> While working on U-Boot for our board we have found problem
>>>>>> related
>>>>>> to CONFIG_API option. In general, enabling it causes build
>>>>>> failure.
>>>>>> Our tests showed that problem exists also on other ARM U-Boot
>>>>>> targets
>>>>>> (for example davinci_dvevm).
>>>>>>
>>>>>> Do you think that this problem may be caused by your libgcc-
>>>>>> related
>>>>>> cleanups ? If so, do you have any idea how to fix it ?
>>>>>
>>>>> sounds more like it's always been a bug, but Jean's cleanup will
>>>>> fix
>>>>> it eventually
>>>>
>>>> CONFIG_API worked fine for ARM builds some time ago, and this
>>>> breakage
>>>> seems like a recent development.
>>>
>>> or, it still works fine if your toolchain doesnt suck and isnt
>>> broken
>>
>> The toolchain is ELDK 4.2 and has worked fine for longer time.
>
> Just to make it clear: The libgcc removal patches for ARM from Jean-
> Christophe
> are not added yet. So if you see a problem with EABI etc, some other
> patches
> have to be the reason for this. And very likely Jean-Christophe's
> patches
> could fix the problems.

Thanks for pointing this out, we'll look into it some more (I'm all
for removing libgcc dependency, but was under the impression that
parts of this rework was already included in main line, and thought
there might be some loose ends or so).

Rafal