From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/grpcio/files/, dev-python/grpcio/
Date: Mon, 8 Jun 2020 07:05:09 +0000 (UTC) [thread overview]
Message-ID: <1591599889.4e00d0a56ca1dd9be9d99a3d80a12d2f0b6b1cfc.gyakovlev@gentoo> (raw)
commit: 4e00d0a56ca1dd9be9d99a3d80a12d2f0b6b1cfc
Author: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 8 06:56:16 2020 +0000
Commit: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Mon Jun 8 07:04:49 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4e00d0a5
dev-python/grpcio: respect CC in setup.py
Upstream-PR: https://github.com/grpc/grpc/pull/23159
Bug: https://bugs.gentoo.org/727478
Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>
dev-python/grpcio/files/setup.py-respect-cc.patch | 33 +++++++++++++++++++++++
dev-python/grpcio/grpcio-1.28.1.ebuild | 2 ++
2 files changed, 35 insertions(+)
diff --git a/dev-python/grpcio/files/setup.py-respect-cc.patch b/dev-python/grpcio/files/setup.py-respect-cc.patch
new file mode 100644
index 00000000000..545346e8152
--- /dev/null
+++ b/dev-python/grpcio/files/setup.py-respect-cc.patch
@@ -0,0 +1,33 @@
+From 0a6c58fc0161e697bbf64b4f3d4ef14b03ac186b Mon Sep 17 00:00:00 2001
+From: Georgy Yakovlev <gyakovlev@gentoo.org>
+Date: Sun, 7 Jun 2020 23:35:31 -0700
+Subject: [PATCH] setup.py: respect CC variable in latomic test
+
+some configurations do not provide generic cc binary.
+while rest of the build calls CHOST prefixed binaries,
+this check fails. fix it.
+
+Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
+---
+ setup.py | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index 2379703eb7..0f92270607 100644
+--- a/setup.py
++++ b/setup.py
+@@ -144,9 +144,10 @@ ENABLE_DOCUMENTATION_BUILD = os.environ.get(
+
+ def check_linker_need_libatomic():
+ """Test if linker on system needs libatomic."""
++ cc = os.environ.get('CC', 'cc')
+ code_test = (b'#include <atomic>\n' +
+ b'int main() { return std::atomic<int64_t>{}; }')
+- cc_test = subprocess.Popen(['cc', '-x', 'c++', '-std=c++11', '-'],
++ cc_test = subprocess.Popen([cc, '-x', 'c++', '-std=c++11', '-'],
+ stdin=PIPE,
+ stdout=PIPE,
+ stderr=PIPE)
+--
+2.27.0
+
diff --git a/dev-python/grpcio/grpcio-1.28.1.ebuild b/dev-python/grpcio/grpcio-1.28.1.ebuild
index 8fd8e8b73c1..52d65ba9345 100644
--- a/dev-python/grpcio/grpcio-1.28.1.ebuild
+++ b/dev-python/grpcio/grpcio-1.28.1.ebuild
@@ -25,6 +25,8 @@ DEPEND="${RDEPEND}
dev-python/setuptools[${PYTHON_USEDEP}]
"
+PATCHES=( "${FILESDIR}/setup.py-respect-cc.patch" )
+
python_configure_all() {
export GRPC_PYTHON_DISABLE_LIBC_COMPATIBILITY=1
export GRPC_PYTHON_BUILD_SYSTEM_CARES=1
next reply other threads:[~2020-06-08 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 7:05 Georgy Yakovlev [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 11:55 [gentoo-commits] repo/gentoo:master commit in: dev-python/grpcio/files/, dev-python/grpcio/ Michał Górny
2020-09-25 22:55 Georgy Yakovlev
2020-03-27 10:42 Michał Górny
2020-01-17 10:22 Georgy Yakovlev
2019-08-17 3:00 Georgy Yakovlev
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=1591599889.4e00d0a56ca1dd9be9d99a3d80a12d2f0b6b1cfc.gyakovlev@gentoo \
--to=gyakovlev@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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