From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-08-30
Date: Sun, 2 Sep 2018 16:57:02 -0300 (BRT) [thread overview]
Message-ID: <241764101.4041403.1535918222698.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20180831060016.342FF22A3A@mail.bootlin.com>
> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "DATACOM" <casantos@datacom.com.br>
> Sent: Friday, August 31, 2018 3:00:16 AM
> Subject: [autobuild.buildroot.net] Your build results for 2018-08-30
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2018-08-30, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
>
> Results for the 'next' branch
> =============================
>
> Build failures related to your packages:
>
> arm | util-linux-2.32.1 |
> http://autobuild.buildroot.net/results/c8e34d661098e96e3f627d7c022fdcf3efa40805
>
> --
> http://autobuild.buildroot.net
I'm still unable to reproduce these "SELinux selected but libselinux
not found or too old" errors.
:-(
--
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
next parent reply other threads:[~2018-09-02 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180831060016.342FF22A3A@mail.bootlin.com>
2018-09-02 19:57 ` Carlos Santos [this message]
2018-09-03 15:29 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-08-30 Matthew Weber
2018-09-03 19:49 ` Matthew Weber
2018-09-04 9:45 ` Thomas Petazzoni
2018-09-04 22:43 ` Arnout Vandecappelle
2018-09-05 6:49 ` Thomas Petazzoni
2018-09-18 21:49 ` 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=241764101.4041403.1535918222698.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--cc=buildroot@busybox.net \
/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