Re: Linking against armlink produced ELF for armv6-m (thumb only) CPU

[Matthew Gretton-Dann <matthew.gretton-dann@arm.com>]

Hi,

The root cause of the issue is that the linker is assuming the wrong 
defaults for an object which does not have a .ARM.attributes section.

There is no one particular build attribute causing the error, it is the 
defaults ld assumes.

One workaround may be to strip all the .ARM.attributes sections out of 
the objects before passing them to the linker:
   arm-none-eabi-objcopy -R '.ARM.attributes' tst.o -o tst.stripped.o

Thanks,

Matt

On 05/07/11 18:49, GusSabina wrote:
>
> Hello Matthew:
>
> I'm getting the same error...
> What ARM Build attribute is explicitly causing this error? How should it be
> fixed?
>
> Thanks
> Gus
>
>
> Matthew Gretton-Dann-2 wrote:
>>
>> On Mon, 2010-08-09 at 18:42 +0300, Heikki Keränen wrote:
>>>
>>
>> The basic issue seems to be that we are treating an object with
>> no .ARM.attributes section as one where all the attributes take their
>> default value (0 or "") and not one which has all the attributes set to
>> undefined (as if a TAG_nodefaults attribute was present).
>>
>> I have raised the following bug in BugZilla to address this:
>> http://sourceware.org/bugzilla/show_bug.cgi?id=11897
>>
>> Thanks,
>>
>> Matt
>>
>> --
>> Matthew Gretton-Dann
>> Principal Engineer - PDSW Tools
>> ARM Ltd
>>
>>
>>
>


-- 
Matthew Gretton-Dann
Principal Engineer, PD Software - Tools, ARM Ltd