Error while building with 4.12 RSB for realview_pbx_a9_qemu

[Sebastian Huber]

Hello Kuan-Hsun,

your tool chain is out of date. Please update it via the RSB.

On 29/07/16 11:22, Kuan Hsun Chen wrote:
> Hello all,
>
> Is there anyone who recently builds up RTEMS source tree for 
> realview_pbx_a9_qemu bsp with 4.12 arm toolchains from RTEMS Source 
> Builder (RSB)?
>
> I used the latest version (commit 
> f383f4bf6eae799794f5cc3eff76a592243d69c8) on the git.
> The command I used:
> "../rtems/configure --target=arm-rtems4.12 
> --enable-rtemsbsp=realview_pbx_a9_qemu --enable-tests=samples 
> --enable-networking --enable-posix 
> --prefix=$HOME/RTEMS-work/compiler/4.12"
>
> I got some errors like (enclosed file has all errors):
>
> ../../cpukit/../../../realview_pbx_a9_qemu/lib/include/rtems/score/basedefs.h:229:5: 
> error: static assertion failed: "THREAD_QUEUE_SYSLOCK_QUEUE_NEXT_TICKET"
>      _Static_assert(cond, # msg)
>      ^
> ../../../../../../rtems/c/src/../../cpukit/score/src/threadq.c:27:1: 
> note: in expansion of macro 'RTEMS_STATIC_ASSERT'
>
> Does any one know how to handle this?
>
> By the way, in RSB, are all 4.11 toolchains are all renamed as 4.12?
> ../source-builder/sb-set-builder --list-bsets
> By following the tutorial on the wiki, it is not possible to repeat 
> the flow with RSB for 4.11 now.
>
> Best,
> Kuan-Hsun
>
> -- 
> M.Sc. Kuan-Hsun Chen
>
> TU Dortmund
> Department of Computer Science 12
> Design Automation of Embedded Systems
> Otto-Hahn-Strasse 16, Room 102
>
> 44227 Dortmund
> Germany
>
> Phone: _+49 231 755 6124_
> Mail: kuan-hsun.chen at tu-dortmund.de <mailto:kuan-hsun.chen at tu-dortmund.de>
>
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users

-- 
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.