4.11 Branch Failures

[Sebastian Huber]

On 21/03/16 06:30, Chris Johns wrote:
> On 21/03/2016 14:40, Joel Sherrill wrote:
>>
>>         (2) There is this group of powerpc BSPs failing on dl01:
>>
>   [snip]
>>     No. If could be rtems-tld. What is the error?
>>
>> mv dl01.pre.exe dl01.pre
>> rtems-syms -e -c "-mcpu=603e -mstrict-align -meabi -msdata=sysv
>> -fno-common -O2 -g -fno-keep-inline-functions -Wall -Wmissing-prototypes
>> -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs" -o
>> dl-sym.o dl01.pre
>> powerpc-rtems4.11-gcc -B../../../../../brs5l/lib/ -specs bsp_specs
>> -qrtems -mcpu=603e -mstrict-align -meabi -msdata=sysv -fno-common -O2 -g
>> -fno-keep-inline-functions -Wall -Wmissing-prototypes
>> -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs
>>   -mcpu=603e -mstrict-align -meabi -msdata=sysv -fno-common   \
>>              -o dl01.exe init.o dl-load.o dl-tar.o dl-sym.o
>> /home/joel/rtems-4.11-work/tools/4.11/lib/gcc/powerpc-rtems4.11/4.9.3/../../../../powerpc-rtems4.11/bin/ld: 
>>
>> dl-sym.o: the target (rtems__rtl_base_globals_size) of a R_PPC_SDAREL16
>> relocation is in the wrong output section (.text)
>> dl-sym.o: In function `rtems_rtl_base_global_syms_init':
>> rld--bTdaaa.c:(.text+0x6): relocation truncated to fit: R_PPC_SDAREL16
>> against `rtems__rtl_base_globals_size'
>> collect2: error: ld returned 1 exit status
>> Makefile:662: recipe for target 'dl01.exe' failed
>
> This means the rtems-syms tool needs to be taught how to create a 
> suitable symbols file for the PowerPC. Sebastian are you able to have 
> a look? 

Its already fixed on the master.

https://git.rtems.org/rtems-tools/commit/?id=f027f37661fc8c12ab07f92982f0c86e4e0717de

 From my point of view we should not use branches for the RTEMS Tools 
and RSB.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.