Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/capnproto: require GCC 5 for C++14
Date: Tue, 10 Sep 2019 12:02:24 +0200	[thread overview]
Message-ID: <20190910120224.5fb7f508@windsurf> (raw)
In-Reply-To: <20190909185215.26744-1-JoelsonCarl@gmail.com>

Hello Joel,

On Mon,  9 Sep 2019 12:52:14 -0600
Joel Carlson <joelsoncarl@gmail.com> wrote:

> Adds dependency on at least GCC 5 to have C++14 language features that
> are required starting in version 0.7.0 of capnproto.
> 
> Fixes:
> http://autobuild.buildroot.org/results/5c09e745cab822d830f73e33647f3b0e765c9181
> (capnproto build failure)
> 
> Fixes:
> http://autobuild.buildroot.org/results/743c750e9932658c20965a25de89c3f21a1d43e9
> (host-capnproto build failure)
> 
> Signed-off-by: Koen Martens <gmc@sonologic.nl>
> Signed-off-by: Joel Carlson <JoelsonCarl@gmail.com>
> 
> ---
> Picking this up from https://patchwork.ozlabs.org/patch/1150841/
> which only changed the config comment dependencies and not the actual
> build dependencies.
> ---
>  package/capnproto/Config.in | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

I've applied both, but after squashing them together. Indeed,
c-capnproto selects capnproto, so applying 1/2 without 2/2 would not
work, so it's really one change.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2019-09-10 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 18:52 [Buildroot] [PATCH 1/2] package/capnproto: require GCC 5 for C++14 Joel Carlson
2019-09-09 18:52 ` [Buildroot] [PATCH 2/2] package/c-capnproto: " Joel Carlson
2019-09-10 10:02 ` 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=20190910120224.5fb7f508@windsurf \
    --to=thomas.petazzoni@bootlin.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