From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-05-06
Date: Tue, 8 May 2018 11:14:47 +0200 [thread overview]
Message-ID: <20180508111447.73787b34@windsurf> (raw)
In-Reply-To: <20180508043238.c3fv3552a7yo26he@tarshish>
Hello,
On Tue, 8 May 2018 07:32:38 +0300, Baruch Siach wrote:
> > > arm | lxc-3.0.0 | NOK | http://autobuild.buildroot.net/results/ef823b0b7dc75e18e6a875d18abbdf530397d02d |
> > > x86_64 | lxc-3.0.0 | NOK | http://autobuild.buildroot.net/results/fc4000c7b348bdc85eab1ce85dcdb9d9dbbbb3cc |
> > > arc | lxc-3.0.0 | NOK | http://autobuild.buildroot.net/results/db50d3490f7f4ef23ac2c41ca98e51fa3ad35bdf |
> > > mips64el | lxc-3.0.0 | NOK | http://autobuild.buildroot.net/results/acc28762239d92184b3ff2aff3be801c1a81eb68 |
> > > sparc64 | lxc-3.0.0 | NOK | http://autobuild.buildroot.net/results/79a885a12e3f73ff5c20f6e3bdf0cd7908fcb3b4 |
> > > arm | lxc-3.0.0 | NOK | http://autobuild.buildroot.net/results/1e361ef5c8ee20a9524d6a204c204b3e19bf5641 |
> >
> > These issues should all be fixed by:
> >
> > 52dcec570e056502c4f9e7b4640bca2bd2db8c23 lxc: fix build with static libcap and shared gnutls
>
> This commit is not is current master as of ba33728bc31.
Argh indeed, my bad. I applied it locally, didn't push it, and then
due to a git reset --hard, it got lost. I've now re-applied that
commit, and pushed this time.
Thanks for the heads-up!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-08 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-05-06 Thomas Petazzoni
2018-05-07 21:46 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-05-07 22:24 ` Fabrice Fontaine
2018-05-08 0:56 ` Matthew Weber
2018-05-08 4:32 ` Baruch Siach
2018-05-08 9:14 ` Thomas Petazzoni [this message]
2018-05-08 9:57 ` Baruch Siach
2018-05-08 12:25 ` 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=20180508111447.73787b34@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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 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.