From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lxc: revive "drop-werror" patch
Date: Mon, 05 Sep 2016 13:05:41 +0200 [thread overview]
Message-ID: <1524184.lBqcmrBiar@sagittea> (raw)
In-Reply-To: <20160903205335.4b1376ca@free-electrons.com>
Hello Thomas,
On Saturday 03 September 2016 20:53:35 Thomas Petazzoni wrote:
> On Sat, 3 Sep 2016 17:24:49 +0200, J?r?me Pouiller wrote:
> > commit 5050a94ae9f448641e05ce29c931671ffdc62784 dropped patch that
> > remove '-Werror' from CFLAGS. However, it seems this patch is still
> > necessary:
> > http://autobuild.buildroot.net/results/b1cbca6d0396863654b1d09ccc3
> > 163c5f6124ab8
> > http://autobuild.buildroot.net/results/fcf2834ad74b95548d25dad227
> > 4704ea401f9665
> > http://autobuild.buildroot.net/results/048be2fc702c9dba9ca4439ff6
> > 87d71b30c10551
> > http://autobuild.buildroot.net/results/939246c9a4f433dfd0dc414988
> > f5957441b8e9b4>
> > Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
> > ---
> >
> > package/lxc/0001-drop-werror.patch | 16 ++++++++++++++++
> > package/lxc/lxc.mk | 2 ++
> > 2 files changed, 18 insertions(+)
> > create mode 100644 package/lxc/0001-drop-werror.patch
>
> Applied to master, thanks. However, could you submit upstream that can
> be accepted? For example, something that adds a --disable-werror
> option.
Unfortunately, it was rejected: https://github.com/lxc/lxc/pull/1168. I
have never been a good advocate.
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2016-09-05 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 15:24 [Buildroot] [PATCH] lxc: revive "drop-werror" patch Jérôme Pouiller
2016-09-03 18:53 ` Thomas Petazzoni
2016-09-05 11:05 ` Jérôme Pouiller [this message]
2016-09-05 19:04 ` Peter Korsgaard
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=1524184.lBqcmrBiar@sagittea \
--to=jezz@sysmic.org \
--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