Build Linux: FAILED 5/bsps/atsamv on x86_64-linux-gnu (rtems-libbsd-v816a2f912f414f39467a6be901a96159f806c01d-x86_64-linux-gnu-1)

[Joel Sherrill]

On Tue, Apr 7, 2020 at 2:04 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

>
> On 07/04/2020 08:24, Chris Johns wrote:
> > On 2020-04-07 15:01, Sebastian Huber wrote:
> >> I am not sure what we should do with this one. The libbsd is well
> >> supported on this BSP, however, with default options, the BSP has not
> >> enough memory to link all the libbsd tests. For this BSP you likely
> >> have to specify some BSP options to build it for your target.
> >
> > What options are required to build libbsd for this BSP? If you say it
> > is well supported a suitable configuration should be possible. The
> > User manual provides no supporting details.
> >
> > Hmmm ... I have not looked at this BSP before now ...
> >
> > ... I see there is README and it contains special options I have never
> > seen before such as `--enable-chip`. I am now wondering how many other
> > magic BSP options exist? Do you know?
>
> My approach to this documentation issue was to address this in the new
> build system. The build specification can be used to generate the user
> manual sections for the BSPs.
>
> >
> > ... The README says "Not all variants are tested" but I cannot see
> > what has been tested? When you are new to a BSP a valid list of what
> > works is important.
> The BSP runs on the evaluation board with default options.
>

But it doesn't build to completion? Why would someone assume a build that
fails produces a working set of exes?

--joel

> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200407/c6ca4a59/attachment.html>