Bug in rtems-tester?

[Chris Johns]

On 12/04/2018 00:39, Joel Sherrill wrote:
> Hi
> 
> These failures have persisted across all the autoconf changes:
> 
> Failures:
>    powerpc/qemuprep-altivec:
>       configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-altivec\
>       --prefix=/home/joel/rtems-work/bsps --enable-networking --enable-smp
>       ld/collect2:0 error: no error message found!
>    powerpc/qemuprep-altivec:
>       configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-altivec\
>       --prefix=/home/joel/rtems-work/bsps --enable-debug --enable-smp
>       ld/collect2:0 error: no error message found!
>    powerpc/qemuprep-altivec:
>       configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-altivec\
>       --prefix=/home/joel/rtems-work/bsps --enable-debug --enable-\
>       networking --enable-smp
>       ld/collect2:0 error: no error message found!
>    powerpc/qemuprep-altivec:
>       configure --target=powerpc-rtems5 --enable-rtemsbsp=qemuprep-altivec\
>       --prefix=/home/joel/rtems-work/bsps --enable-smp
>       ld/collect2:0 error: no error message found!
> 
> 
> I checked and it looks like qemuprep-altivec is listed in the smp excludes section.
> 

Yes that does look like a bug.

The second bug is the rather average error message.

> It is the only BSP with a - in the name that is in smp-excludes. Could it be
> that the matching fails in this case?
> 
> The other is pc586-sse which is SMP excluded also but using a different mechanism..

Could you please raise a ticket?

Thanks
Chris