All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Martens <gmc@sonologic.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/capnproto: increase gcc version dependency
Date: Wed, 21 Aug 2019 15:21:54 +0200	[thread overview]
Message-ID: <20190821132153.GC26497@coltrane> (raw)

The new version of capnproto requires c++14, therefore
the dependency has been increase from at least gcc 4.8
to at least gcc 5.x.

This patch should be applied to a branch that already
has the patch that increases the capnproto version to
0.7.0. At the time of writing this, that means the next
branch.

Signed-off-by: Koen Martens <gmc@sonologic.nl>
---
 package/capnproto/Config.in | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/package/capnproto/Config.in b/package/capnproto/Config.in
index a979a334ff..a81b7c9d96 100644
--- a/package/capnproto/Config.in
+++ b/package/capnproto/Config.in
@@ -15,10 +15,10 @@ config BR2_PACKAGE_CAPNPROTO
 
 	  https://capnproto.org/index.html
 
-comment "capnproto needs host and target gcc >= 4.8 w/ C++, threads, atomic"
+comment "capnproto needs host and target gcc >= 5 w/ C++, threads, atomic"
 	depends on BR2_USE_MMU
-	depends on !BR2_HOST_GCC_AT_LEAST_4_8 || \
-		!BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 || \
+	depends on !BR2_HOST_GCC_AT_LEAST_5 || \
+		!BR2_TOOLCHAIN_GCC_AT_LEAST_5 || \
 		!BR2_INSTALL_LIBSTDCPP || \
 		!BR2_TOOLCHAIN_HAS_THREADS || \
 		!BR2_TOOLCHAIN_HAS_ATOMIC
-- 
2.17.1

             reply	other threads:[~2019-08-21 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 13:21 Koen Martens [this message]
2019-09-02 18:06 ` [Buildroot] [PATCH 1/1] package/capnproto: increase gcc version dependency Koen Martens
2019-09-10 10:41   ` Thomas Petazzoni
2019-09-10 10:04 ` Thomas Petazzoni

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=20190821132153.GC26497@coltrane \
    --to=gmc@sonologic.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.