From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Asaf Kahlon <asafka7@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/python-cryptography: depend comment on BR2_PACKAGE_PYTHON3
Date: Sun, 15 Aug 2021 22:53:35 +0300 [thread overview]
Message-ID: <20210815195340.12027-1-asafka7@gmail.com> (raw)
The user shouldn't view the comment on the python2 menu.
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
package/python-cryptography/Config.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/python-cryptography/Config.in b/package/python-cryptography/Config.in
index 5a2e6da900..da4252d6da 100644
--- a/package/python-cryptography/Config.in
+++ b/package/python-cryptography/Config.in
@@ -17,4 +17,5 @@ config BR2_PACKAGE_PYTHON_CRYPTOGRAPHY
https://cryptography.io
comment "python-cryptography needs a toolchain w/ C++"
+ depends on BR2_PACKAGE_PYTHON3
depends on !BR2_INSTALL_LIBSTDCPP
--
2.30.2
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next reply other threads:[~2021-08-15 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 19:53 Asaf Kahlon [this message]
2021-08-15 19:53 ` [Buildroot] [PATCH 1/1] package/python-keyring: depend comment on BR2_PACKAGE_PYTHON3 Asaf Kahlon
2021-08-15 19:53 ` [Buildroot] [PATCH 1/1] package/python-pyopenssl: " Asaf Kahlon
2021-08-15 19:53 ` [Buildroot] [PATCH 1/1] package/python-secretstorage: " Asaf Kahlon
2021-09-04 21:47 ` Peter Korsgaard
2021-08-15 19:53 ` [Buildroot] [PATCH 1/1] package/python-service-identity: " Asaf Kahlon
2021-08-15 19:53 ` [Buildroot] [PATCH 1/1] package/python-treq: " Asaf Kahlon
2021-08-17 19:58 ` [Buildroot] [PATCH 1/1] package/python-cryptography: " Yann E. MORIN
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=20210815195340.12027-1-asafka7@gmail.com \
--to=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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