From: Rahul Bedarkar <Rahul.Bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] logrotate: fix up build error with gcc 6
Date: Fri, 19 Aug 2016 11:14:30 +0530 [thread overview]
Message-ID: <57B69CBE.2040305@imgtec.com> (raw)
In-Reply-To: <20160818212125.1cb8e7ae@free-electrons.com>
Hi Thomas,
On Friday 19 August 2016 12:51 AM, Thomas Petazzoni wrote:
> Hello,
>
> Can this apply without the 3.10.0 bump?
Yes, but this patch fixes only one build error out of two.
We see following two build errors
logrotate.c: In function 'postrotateSingleLog':
logrotate.c:1784:5: error: this 'if' clause does not guard...
[-Werror=misleading-indentation]
if (!state->doRotate)
^~
logrotate.c:1787:2: note: ...this statement, but the latter is
misleadingly indented as if it is guarded by the 'if'
if (!hasErrors && log->flags & LOG_FLAG_TMPFILENAME) {
^~
config.c: In function 'strndup':
config.c:87:10: error: nonnull argument 's' compared to NULL
[-Werror=nonnull-compare]
if(!s)
^
cc1: all warnings being treated as errors
make[2]: *** [config.o] Error 1
make[2]: *** Waiting for unfinished jobs....
cc1: all warnings being treated as errors
make[2]: *** [logrotate.o] Error 1
Another build error is fixed in upstream so PATCH 1/2 does version bump.
Upstream commit -
https://github.com/logrotate/logrotate/commit/6a36c105587b07ad14fc937f3ee6e2eb402621a2
>
> Indeed PATCH 2/2 being a bug fix, it would be a candidate for the
> "master" branch, while PATCH 1/2 being a version bump, we can only
> commit it to the "next" branch.
In that case, I will spin v2 of this patch and backport upstream commit
to fix second build error.
Thanks,
Rahul
next prev parent reply other threads:[~2016-08-19 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 17:04 [Buildroot] [PATCH 1/2] logrotate: bump version to 3.10.0 Rahul Bedarkar
2016-08-18 17:04 ` [Buildroot] [PATCH 2/2] logrotate: fix up build error with gcc 6 Rahul Bedarkar
2016-08-18 19:21 ` Thomas Petazzoni
2016-08-19 5:44 ` Rahul Bedarkar [this message]
2016-08-19 10:27 ` 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=57B69CBE.2040305@imgtec.com \
--to=rahul.bedarkar@imgtec.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.