Build Failures on Master

[Joel Sherrill]

On Wed, Jan 31, 2018 at 5:40 AM, Sebastian Huber <
sebastian.huber at 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
>>>
>>
>> The problems seem to be an issue with the BSP builder:
>>
>> ../configure --target=powerpc-rtems5 --enable-rtemsbsp=qoriq_e6500_64
>> ss555
>> configure: WARNING: you should use --build, --host, --target
>> configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
>> checking for gmake... gmake
>> checking for RTEMS Version... 5.0.0
>> checking build system type... Invalid configuration `ss555': machine
>> `ss555' not recognized
>> configure: error: /bin/sh /home/EB/sebastian_h/git-rtems/./config.sub
>> ss555 failed
>>
>
Weird. 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.

/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?


>
> The above is one issue. The below is another issue.
>
>
>
>> On powerpc only the qoriq and t32mppc BSPs support SMP. How does the BSP
>> builder know that SMP is supported for a particular BSP?
>>
>
This is a Chris question.

>
>>
> --
> 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180131/56083599/attachment-0002.html>