Re: [Buildroot] Analysis of build results for 2021-08-17

[Thomas Petazzoni <thomas.petazzoni@bootlin.com>]

Hello Arnout,

On Thu, 19 Aug 2021 11:27:27 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>  Fixed by 93351fa0b3b8b6dd10faa9a15a7a173b92cb40a0. It's not obvious since the
> fix is actually in fontconfig, not cairo.

Ah good.

> >>    mipsel    |         openmpi-4.0.0          | NOK | http://autobuild.buildroot.net/results/2f96654c2238c115060aafc3cf10f71457c585f7 | ORPH  
> > 
> > checking alignment of Fortran type(test_mpi_handle)... configure: error: Can not determine alignment of type(test_mpi_handle) when cross-compiling
> > 
> > Gwenhael, Arnout, you are the folks who looked at Fortran stuff :-)  
> 
>  Hehe. It's not really fortran stuff, it's just cross-compilation. Probably
> needs an ac_cv setting, possibly a patch to enable it.

This stuff is built with CMake, so it's probably not an ac_cv_ variable.

> >>   riscv32    |         qt5base-5.15.2         | NOK | http://autobuild.buildroot.net/results/568f7fceebb06deb0755e8d3757c761608faeec7 |       
> > 
> > thread/qfutex_p.h:116:30: error: '__NR_futex' was not declared in this scope; did you mean '_q_futex'?
> >   116 |         int result = syscall(__NR_futex, addr, op | FUTEX_PRIVATE_FLAG, val, val2, addr2, val3);
> >       |                              ^~~~~~~~~~
> >       |                              _q_futex
> > 
> > Need to explore why __NR_futex is not available on RISC-V 32-bit and
> > what we're supposed to use instead.  
> 
>  __NR_futex64, but it's not as simple as that because you also need to make sure
> 64-bit time_t is used as an argument.

Should we disable Qt5 on RISC-V 32-bit ?

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot