From: Michael Nosthoff <buildroot@heine.tech>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/libabseil-cpp: enforce C++11
Date: Fri, 30 Oct 2020 12:25:04 +0100 [thread overview]
Message-ID: <20201030112506.489-1-buildroot@heine.tech> (raw)
Abseil needs at least c++11 but removed the fallback when not set in [0].
So we need to do this.
[0] https://github.com/abseil/abseil-cpp/commit/c6954897f7ece5011f0126db9117361dc1a6ff36
Fixes:
http://autobuild.buildroot.net/results/5780d5e21e5e9c0ba86cc422ef995f45dc83cc4c
http://autobuild.buildroot.net/results/8138c63fc13940e1b97f07f24752b199f88ccfa8
http://autobuild.buildroot.net/results/f8eda966c6400c242680db378c8944444d89d5c5
http://autobuild.buildroot.net/results/38e9427d995e16bc4876f9fdc890c42e4fd04c06
http://autobuild.buildroot.net/results/4e99415728a6f3c6b396a9872924262652f77996
http://autobuild.buildroot.net/results/1830577843772bdfd6e310b4d361aa1edf5969d6
Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
---
package/libabseil-cpp/libabseil-cpp.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/libabseil-cpp/libabseil-cpp.mk b/package/libabseil-cpp/libabseil-cpp.mk
index dfcf892f65..9cff8f0ff4 100644
--- a/package/libabseil-cpp/libabseil-cpp.mk
+++ b/package/libabseil-cpp/libabseil-cpp.mk
@@ -11,11 +11,13 @@ LIBABSEIL_CPP_LICENSE_FILES = LICENSE
LIBABSEIL_CPP_INSTALL_STAGING = YES
LIBABSEIL_CPP_CONF_OPTS = \
+ -DCMAKE_CXX_STANDARD=11 \
-DABSL_ENABLE_INSTALL=ON \
-DABSL_USE_GOOGLETEST_HEAD=OFF \
-DABSL_RUN_TESTS=OFF
HOST_LIBABSEIL_CPP_CONF_OPTS = \
+ -DCMAKE_CXX_STANDARD=11 \
-DABSL_ENABLE_INSTALL=ON \
-DABSL_USE_GOOGLETEST_HEAD=OFF \
-DABSL_RUN_TESTS=OFF
--
2.25.1
next reply other threads:[~2020-10-30 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 11:25 Michael Nosthoff [this message]
2020-10-30 11:25 ` [Buildroot] [PATCH v2 2/2] package/libabseil-cpp: depend on (host) gcc >= 4.9 Michael Nosthoff
2020-10-31 21:21 ` [Buildroot] [PATCH v2 1/2] package/libabseil-cpp: enforce C++11 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=20201030112506.489-1-buildroot@heine.tech \
--to=buildroot@heine.tech \
--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.