From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2021-08-17
Date: Wed, 18 Aug 2021 12:25:11 +0200 [thread overview]
Message-ID: <20210818122511.005d6a5c@windsurf> (raw)
In-Reply-To: <20210818065730.330904074D@smtp4.osuosl.org>
Hello,
On Wed, 18 Aug 2021 06:57:22 -0000
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Detail of failures for next
> ---------------------------
>
> arch | reason | OK? | url | orph?
> -------------+--------------------------------+-----+---------------------------------------------------------------------------------+-------
[...]
> sparc | host-libcap-2.52 | NOK | http://autobuild.buildroot.net/results/c5013a4d9a7dd2305bab8d9aa43104fd5f353bcf |
> arc | host-libcap-2.52 | NOK | http://autobuild.buildroot.net/results/2511a7ec0b4fc29133a4fc99160beb47c5681f02 |
> powerpc | host-libcap-2.52 | NOK | http://autobuild.buildroot.net/results/e0d8cb350072ea90c331824a6790c792d60d885d |
I am confused by these host-libcap issues, as I'm not able to
reproduce. I tried on my local machine, and the host binaries have the
proper RPATH. Thinking it might be a machine/distro specific issue, I
tried on the gcc160 machine, which has reported build issues, and I
tried building the exact defconfig of one of the build failures, and
host-libcap builds just fine.
So, I'm confused :/ Any idea ?
Thomas
--
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
next prev parent reply other threads:[~2021-08-18 10:25 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 [this message]
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
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=20210818122511.005d6a5c@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox