All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] git-crypt: disable for gcc affected by bug #64735
Date: Tue, 28 Aug 2018 14:17:42 +0300	[thread overview]
Message-ID: <3ba001ca8c4a2e548c47bdb7b52573b4ab2803a8.1535455062.git.baruch@tkos.co.il> (raw)

git-crypt needs exception_ptr. gcc older than 7 don't provide that on
all architectures due to gcc bug #64735.

Fixes:
http://autobuild.buildroot.net/results/2a7/2a76ce39bc639b4f17ff33f8447d9094215e68d8/

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
 package/git-crypt/Config.in | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/package/git-crypt/Config.in b/package/git-crypt/Config.in
index bb86219cf89f..9a270b8f9d07 100644
--- a/package/git-crypt/Config.in
+++ b/package/git-crypt/Config.in
@@ -2,6 +2,7 @@ config BR2_PACKAGE_GIT_CRYPT
 	bool "git-crypt"
 	depends on BR2_INSTALL_LIBSTDCPP
 	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # C++11
+	depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_64735 # exception_ptr
 	depends on BR2_USE_MMU # git
 	select BR2_PACKAGE_GIT # runtime
 	select BR2_PACKAGE_OPENSSL
@@ -15,3 +16,7 @@ comment "git-crypt needs a toolchain w/ C++, gcc >= 4.9"
 	depends on !BR2_INSTALL_LIBSTDCPP \
 		|| !BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
 	depends on BR2_USE_MMU
+
+comment "git-crypt needs a toolchain not affected by GCC bug 64735"
+	depends on BR2_USE_MMU
+	depends on BR2_TOOLCHAIN_HAS_GCC_BUG_64735
-- 
2.18.0

             reply	other threads:[~2018-08-28 11:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 11:17 Baruch Siach [this message]
2018-08-28 21:08 ` [Buildroot] [PATCH next] git-crypt: disable for gcc affected by bug #64735 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=3ba001ca8c4a2e548c47bdb7b52573b4ab2803a8.1535455062.git.baruch@tkos.co.il \
    --to=baruch@tkos.co.il \
    --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.