This just means it doesn't have a bset. It doesn't mean it works. It still
is present in libbsd.
It will just now fail when someone performs the same steps by hand. I don't
see removing the bset as the solution.
I do not propose removing it from libbsd or the bsets. There needs to be a
mechanism like the tcfg logic to disable specific tests for specific BSPs
in libbsd.
--joel
On Tue, Apr 7, 2020 at 8:40 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> It is not possible to build libbsd with the standard settings of this
> BSP. The BSP is also highly configurable and it is unlikely that the
> RSB built configuration runs on a custom board.
> ---
> rtems/config/5/bsps/atsamv.bset | 10 ----------
> 1 file changed, 10 deletions(-)
> delete mode 100644 rtems/config/5/bsps/atsamv.bset
>
> diff --git a/rtems/config/5/bsps/atsamv.bset
> b/rtems/config/5/bsps/atsamv.bset
> deleted file mode 100644
> index 4bde317..0000000
> --- a/rtems/config/5/bsps/atsamv.bset
> +++ /dev/null
> @@ -1,10 +0,0 @@
> -%define mail_single_report 1
> -
> -%define with_rtems_bsp atsamv
> -%define rtems_target arm-rtems5
> -%define rtems_host %{rtems_target}
> -
> -5/rtems-arm
> -5/rtems-kernel
> -5/rtems-libbsd
> -5/rtems-packages
> --
> 2.16.4
>
> _______________________________________________
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
