From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next] package/apitrace: bump version
Date: Mon, 22 May 2017 15:59:22 +0200 [thread overview]
Message-ID: <20170522155922.1eeb98d7@free-electrons.com> (raw)
In-Reply-To: <20170521171101.14097-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 21 May 2017 19:11:01 +0200, Bernd Kuhls wrote:
> Currently we have version 7.0, released July 2015. Latest upstream
> release 7.1, which dates back to November 2015, causes build errors.
>
> Therefore we bump to git HEAD, updated May 2017, which builds fine.
>
> The package requires gcc-4.9 or later now:
> https://github.com/apitrace/apitrace/commit/2940c642832ba9dd0322a351034a2c52331e6e2b
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/apitrace/Config.in | 6 +++---
> package/apitrace/apitrace.hash | 2 +-
> package/apitrace/apitrace.mk | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-22 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 17:11 [Buildroot] [PATCH/next] package/apitrace: bump version Bernd Kuhls
2017-05-22 13:59 ` Thomas Petazzoni [this message]
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=20170522155922.1eeb98d7@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