From: Andrew Whatson via Guix-patches via <guix-patches@gnu.org>
To: 63243@debbugs.gnu.org
Cc: Andrew Whatson <whatson@tailcall.au>
Subject: [bug#63243] [PATCH] gnu: bear: Build against 'abseil-cpp-cxxstd11'.
Date: Wed, 3 May 2023 16:43:35 +1000 [thread overview]
Message-ID: <85ebc606e3a576dec1497b1a3ff141d3e4ea6193.1683096215.git.whatson@tailcall.au> (raw)
Fixes a linker error when building bear, caused by incompatibility
between abseil-cpp used by bear and abseil-cpp-cxxstd11 used by grpc.
* gnu/packages/build-tools.scm (bear)[native-inputs]: Use
ABSEIL-CPP-CXXSTD11.
---
gnu/packages/build-tools.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnu/packages/build-tools.scm b/gnu/packages/build-tools.scm
index bcca229466..33d91e6043 100644
--- a/gnu/packages/build-tools.scm
+++ b/gnu/packages/build-tools.scm
@@ -154,7 +154,7 @@ (define-public bear
("re2" ,re2)
("spdlog" ,spdlog-1.10)))
(native-inputs
- `(("abseil-cpp" ,abseil-cpp)
+ `(("abseil-cpp" ,abseil-cpp-cxxstd11)
("googletest" ,googletest)
("openssl" ,openssl)
("pkg-config" ,pkg-config)
base-commit: 94e2e3553440a2a5ac4a312e80b8ea21ddebafeb
prerequisite-patch-id: 3d7fb3e786cac039448473f020bca5a1ba784ba7
prerequisite-patch-id: 9e65215b0ab7e634442ffb20fa51c062754fef36
prerequisite-patch-id: e6f89e5aa48e27e1a05bb25cdf7306904fb97b87
prerequisite-patch-id: dea0b27507762194e6d3323ee383375ce9bb5b3f
prerequisite-patch-id: 4a151f7ab214688100ad9be43cc517d4e83fae5b
prerequisite-patch-id: aa79730a845863aa68c4413f01e9957159d9b37b
prerequisite-patch-id: c991685207a07ca27bf7add0ac6b931919e35652
--
2.39.2
next reply other threads:[~2023-05-03 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 6:43 Andrew Whatson via Guix-patches via [this message]
2023-05-05 21:53 ` bug#63243: [PATCH] gnu: bear: Build against 'abseil-cpp-cxxstd11' Ludovic Courtès
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=85ebc606e3a576dec1497b1a3ff141d3e4ea6193.1683096215.git.whatson@tailcall.au \
--to=guix-patches@gnu.org \
--cc=63243@debbugs.gnu.org \
--cc=whatson@tailcall.au \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.