[PATCH] 6: Add unstable RTEMS 6 tool chain

[Chris Johns]

On 7/1/19 11:58 pm, Sebastian Huber wrote:
> I was able to build all tools except epiphany on a FreeBSD 11 machine. I built
> the erc32 BSP and did a test run. One problem was this:
> 
> rtems-test --rtems-bsp=erc32 --rtems-tools=/opt/rtems/6 /home/user/build/b-erc32
> RTEMS Testing - Tester, 5.0.not_released
>  Command Line: /opt/rtems/6/bin/rtems-test --rtems-bsp=erc32
> --rtems-tools=/opt/rtems/6 /home/user/build/b-erc32
>  Python: 2.7.12 (default, Oct 29 2016, 13:38:04) [GCC 4.2.1 Compatible FreeBSD
> Clang 3.8.0 (tags/RELEASE_380/final 262564)]
> Host: FreeBSD-11.1-RELEASE-p1-amd64-64bit-ELF (FreeBSD FreeBSDBuild
> 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug  9 11:55:48 UTC 2017
> root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 amd64)
> [  3/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> whetstone.exe
> [  6/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> fsdosfsformat01.exe
> [  1/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> dhrystone.exe
> [  2/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> linpack.exe
> [  5/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> fsclose01.exe
> [  4/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> fsbdpart01.exe
> [  8/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> fsdosfsname02.exe
> [  7/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | sparc/erc32:
> fsdosfsname01.exe
> error: gdb exec: /opt/rtems/6/bin/sparc-rtems5-gdb: No such file or directory
> 

Ouch.

> I fixed this with a symbolic link:
> 
> ln -s /opt/rtems/6/bin/sparc-rtems6-gdb /opt/rtems/6/bin/sparc-rtems5-gdb

I thought there was a version option but I cannot see it. Please raise a ticket
on me to add a --version option to allow this to handled cleanly.

> I will try to automate this to get a weekly update.

What is updated each week?

> What do we want to do with failing targets? 

The tier structure should handle this.

> I will probably take care of the
> main stream targets, but what about epiphany?

The arch is placed in tier 5 for a release and removed after the release is made.

Chris