From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/kodi-pvr-stalker: fix gcc7 compile
Date: Thu, 8 Jun 2017 23:36:48 +0200 [thread overview]
Message-ID: <20170608233648.5e0722fb@free-electrons.com> (raw)
In-Reply-To: <20170513182944.29833-1-bernd.kuhls@t-online.de>
Hello,
On Sat, 13 May 2017 20:29:44 +0200, Bernd Kuhls wrote:
> diff --git a/package/kodi-pvr-stalker/0001-src-CWatchdog.h-Fix-gcc7-build.patch b/package/kodi-pvr-stalker/0001-src-CWatchdog.h-Fix-gcc7-build.patch
> new file mode 100644
> index 0000000000..54d18a996c
> --- /dev/null
> +++ b/package/kodi-pvr-stalker/0001-src-CWatchdog.h-Fix-gcc7-build.patch
> @@ -0,0 +1,33 @@
> +From bb16ccd14deb3a01049daec37b6d2e7711ef4738 Mon Sep 17 00:00:00 2001
> +From: Bernd Kuhls <bernd.kuhls@t-online.de>
> +Date: Sat, 13 May 2017 20:22:08 +0200
> +Subject: [PATCH 1/1] src/CWatchdog.h: Fix gcc7 build
Please use [PATCH] instead of [PATCH 1/1], i.e use git format-patch -N.
> +Building with gcc7 is broken:
> +
> +src/CWatchdog.h:31:58: error: 'std::function' has not been declared
> + CWatchdog(unsigned int interval, SAPI *api, std::function<void(SError)> errorCallback);
> + ^~~~~~~~
> +
> +Patch sent upstream as PR 93.
A link is better than "PR 93".
I've fixed both, and applied, after also adjusting DOS line endings as
you mentioned (I tested that the patch applies properly).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-08 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 18:29 [Buildroot] [PATCH/next 1/1] package/kodi-pvr-stalker: fix gcc7 compile Bernd Kuhls
2017-05-14 13:38 ` Bernd Kuhls
2017-06-08 21:36 ` Thomas Petazzoni [this message]
2017-06-09 4:07 ` Bernd Kuhls
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=20170608233648.5e0722fb@free-electrons.com \
--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