All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org,
	 Matthew Weber <matthew.weber@rockwellcollins.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Adam Duskett <aduskett@gmail.com>,
	Herve Codina <herve.codina@bootlin.com>,
	Giulio Benetti <giulio.benetti@micronovasrl.com>,
	Bernd Kuhls <bernd.kuhls@t-online.de>,
	Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
	Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] Analysis of build results for 2021-08-17
Date: Thu, 19 Aug 2021 11:27:27 +0200	[thread overview]
Message-ID: <4660a41d-6111-05aa-4b82-274391cd7bd9@mind.be> (raw)
In-Reply-To: <20210818234453.03d2237a@windsurf>



On 18/08/2021 23:44, Thomas Petazzoni wrote:
[snip]
>>    xtensa    |       host-cairo-1.16.0        | NOK | http://autobuild.buildroot.net/results/00096bad2d9eee90c07761fc8c7f9eafe8782dac |     
>>   mips64el   |       host-cairo-1.16.0        | NOK | http://autobuild.buildroot.net/results/c1d61387edf1f79522f7d9df82c90c9cd67bba2d |     
> 
> cannot delete non-empty directory: share/gettext
> could not make way for new symlink: share/gettext
> 
> Seems like a per-package issue. Hm, I think Fabrice you looked into
> this. Hervé, any input?

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

[snip]
>>    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.


[snip]
>>   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.


 Regards,
 Arnout

[snip]
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-08-19  9:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  6:57 [Buildroot] [autobuild.buildroot.net] Daily results for 2021-08-17 Thomas Petazzoni
2021-08-18 10:25 ` Thomas Petazzoni
2021-08-18 11:05   ` Yann E. MORIN
2021-08-18 20:18     ` Thomas Petazzoni
2021-08-18 21:04       ` Yann E. MORIN
2021-08-23 20:55         ` Arnout Vandecappelle
2021-08-23 22:06           ` Thomas Petazzoni
2021-08-23 22:16             ` Arnout Vandecappelle
2021-08-18 21:44 ` [Buildroot] Analysis of build " Thomas Petazzoni
2021-08-18 22:24   ` Giulio Benetti
2021-08-18 22:26     ` Giulio Benetti
2021-08-19  0:01     ` Giulio Benetti
2021-08-19 13:28     ` Thomas Petazzoni
2021-08-20 14:26       ` Giulio Benetti
2021-08-20 22:00         ` Giulio Benetti
2021-08-21 23:08     ` Giulio Benetti
2021-08-19  9:27   ` Arnout Vandecappelle [this message]
2021-08-19 13:24     ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4660a41d-6111-05aa-4b82-274391cd7bd9@mind.be \
    --to=arnout@mind.be \
    --cc=aduskett@gmail.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=fontaine.fabrice@gmail.com \
    --cc=giulio.benetti@micronovasrl.com \
    --cc=gwenhael.goavec-merou@trabucayre.com \
    --cc=herve.codina@bootlin.com \
    --cc=matthew.weber@rockwellcollins.com \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.