Build Failures on Master

Joel Sherrill joel at rtems.org
Wed Jan 31 22:14:15 UTC 2018


On Wed, Jan 31, 2018 at 3:58 PM, Chris Johns <chrisj at rtems.org> wrote:

>
>
> On 01/02/2018 03:14, Joel Sherrill wrote:
> >
> >
> > On Wed, Jan 31, 2018 at 5:40 AM, Sebastian Huber
> > <sebastian.huber at embedded-brains.de <mailto:sebastian.huber@
> embedded-brains.de>>
> > wrote:
> >
> >
> >
> >     On 31/01/18 12:09, Sebastian Huber wrote:
> >
> >         On 27/01/18 23:49, Joel Sherrill wrote:
> >
> >             Hi
> >
> >             This bsp builder test report shows about 25 build failures.
> >
> >             https://lists.rtems.org/pipermail/build/2018-January/
> 000333.html
> >             <https://lists.rtems.org/pipermail/build/2018-January/
> 000333.html>
> >
> >
> >         The problems seem to be an issue with the BSP builder:
> >
> >         ../configure --target=powerpc-rtems5
> --enable-rtemsbsp=qoriq_e6500_64 ss555
>
> https://git.rtems.org/rtems-tools/tree/tester/rtems/rtems-
> bsps-powerpc.ini#n45
>
> No ',' at the end of the line. An easy mistake and so I would like to add
> an
> error check to the BSP builder.
>
> I will sort this out. I would like to use this as a test case to add a
> check for
> spaces in BSP names.
>

Did you see this in my earlier reply?

I did another build overnight and I don't see it in the list archives by
date. But when I
go by author, I see it. There are failures in it that I can't reproduce by
hand.

https://lists.rtems.org/pipermail/build/2018-January/000376.html

Specifically I tried the first one on the list and it build for me this
morning. This
is listed as a failure but not when I build by hand.

/home/joel/rtems-work/rtems/configure --target=arm-rtems5\
>       --enable-rtemsbsp=arm1136jfs --prefix=/home/joel/rtems-work/bsps\
>       --enable-debug

Can anyone explain the difference?




>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180131/6179163f/attachment-0001.html>


More information about the devel mailing list