Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/faketime: fix build with gcc >= 6
Date: Tue, 16 May 2017 08:41:59 +0200	[thread overview]
Message-ID: <87wp9h8frc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <60001b91-3306-48fb-4973-bf16d3b02f01@gmail.com> (Romain Naour's message of "Mon, 15 May 2017 22:36:10 +0200")

>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:

Hi,

 >> > +[Romain: rebase on 0.9.6]
 >> > +Signed-off-by: Romain Naour <romain.naour@gmail.com>
 >> 
 >> It is nice if you use the -x option to git cherry-pick so it adds a
 >> comment about the original git commit id. I've now manually added it.

 > Well, sometime I just use git format-patch -1 HASH when the patch apply cleanly
 > without creating a new branch and cherry-picking. In that case there is no -x
 > option...

No, but in that case you are not rebasing, so the git hash listed in the
commit is the correct one. The -x option is only when you rebase /
cherry-pick for traceability.

>>> +---
 >> > + src/Makefile | 2 +-
 >> > + 1 file changed, 1 insertion(+), 1 deletion(-)
 >> > +
 >> > +diff --git a/src/Makefile b/src/Makefile
 >> > +index 51634b0..bbbd476 100644
 >> > +--- a/src/Makefile
 >> > ++++ b/src/Makefile
 >> > +@@ -67,7 +67,7 @@ INSTALL ?= install
 >> > + PREFIX ?= /usr/local
 >> > + LIBDIRNAME ?= /lib/faketime
 >> > + 
 >> > +-CFLAGS += -std=gnu99 -Wall -Wextra -Werror -DFAKE_STAT
 >> > -DFAKE_SLEEP -DFAKE_TIMERS -DFAKE_INTERNAL_CALLS -fPIC
 >> > -DPREFIX='"'$(PREFIX)'"' -DLIBDIRNAME='"'$(LIBDIRNAME)'"'
 >> > ++CFLAGS += -std=gnu99 -Wall -Wextra -Werror -Wno-nonnull-compare
 >> > -DFAKE_STAT -DFAKE_SLEEP -DFAKE_TIMERS -DFAKE_INTERNAL_CALLS
 >> > -fPIC -DPREFIX='"'$(PREFIX)'"' -DLIBDIRNAME='"'$(LIBDIRNAME)'"'
 >> 
 >> The -Wall -Werror flags are not so nice, but oh well.

 > ha yes... do you want I send a new patch removing Werror instead ?

So far we don't seem to have any build failures from it (besides this
one), so it isn't strictly needed - Just a potential problem.

I would leave it as is for now, unless if we can convince upstream to
accept such a patch.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-05-16  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14 21:26 [Buildroot] [PATCH] package/faketime: fix build with gcc >= 6 Romain Naour
2017-05-15 18:24 ` Peter Korsgaard
2017-05-15 20:36   ` Romain Naour
2017-05-16  6:41     ` Peter Korsgaard [this message]
2017-05-17 20:35 ` 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=87wp9h8frc.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox