From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH (2017.05.x)] protobuf: don't download patch from Github
Date: Wed, 19 Jul 2017 22:39:06 +0200 [thread overview]
Message-ID: <20170719223906.764e5ccf@windsurf> (raw)
In-Reply-To: <1500496210-2946-1-git-send-email-casantos@datacom.ind.br>
Hello,
On Wed, 19 Jul 2017 17:30:10 -0300, Carlos Santos wrote:
> Patches downloaded from Github are not stable, so bring them in the
> tree.
>
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
> package/protobuf/0001-Fix-freebsd-build.patch | 143 ++++++++++++++++++++++++++
> package/protobuf/protobuf.hash | 1 -
> package/protobuf/protobuf.mk | 2 -
> 3 files changed, 143 insertions(+), 3 deletions(-)
> create mode 100644 package/protobuf/0001-Fix-freebsd-build.patch
>
> diff --git a/package/protobuf/0001-Fix-freebsd-build.patch b/package/protobuf/0001-Fix-freebsd-build.patch
> new file mode 100644
> index 0000000..0cdcfa6
> --- /dev/null
> +++ b/package/protobuf/0001-Fix-freebsd-build.patch
> @@ -0,0 +1,143 @@
> +From 416f90939d4de58fe1a4e2489120010313183291 Mon Sep 17 00:00:00 2001
> +From: Feng Xiao <xfxyjwf@gmail.com>
> +Date: Tue, 14 Mar 2017 23:12:52 +0000
> +Subject: [PATCH] Fix freebsd build.
> +
> +It turns out system headers included by generated plugin.pb.h file already contains
> +major/minor macro definitions when built on FreeBSD and we need to add #undefs to
> +the generated header file.
> +
> +This change also fixes another compile error regarding EXPECT_DEATH on FreeBSD.
We need your SoB here.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-19 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 20:30 [Buildroot] [PATCH (2017.05.x)] protobuf: don't download patch from Github Carlos Santos
2017-07-19 20:39 ` Thomas Petazzoni [this message]
2017-07-20 10:57 ` [Buildroot] [PATCH v2 " Carlos Santos
2017-07-20 13:12 ` 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=20170719223906.764e5ccf@windsurf \
--to=thomas.petazzoni@free-electrons.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