All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Breese <jack@kumunetworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gnupg: Add options for SHA-256 and SHA-512 hashes
Date: Thu,  6 Apr 2017 18:09:43 -0700	[thread overview]
Message-ID: <20170407010943.80192-1-jack@kumunetworks.com> (raw)
In-Reply-To: <20170406010908.95234-1-jack@kumunetworks.com>

Signed-off-by: Jack Breese <jack@kumunetworks.com>

---
Changes v1 -> v2:
 - Enable SHA-256 and SHA-512 unconditionally because
   size difference is small. (~6k on armv7l) (Suggested by Baruch)

Binary size without SHA256 + SHA512:
-rwxr-xr-x 1 root root 550K Apr  6 10:03 gpg

Binary size with both:
-rwxr-xr-x 1 root root 555.9K Mar 31 22:50 gpg

Signed-off-by: Jack Breese <jack@kumunetworks.com>
---
 package/gnupg/gnupg.mk | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/package/gnupg/gnupg.mk b/package/gnupg/gnupg.mk
index caa9d2c46..b3578b87d 100644
--- a/package/gnupg/gnupg.mk
+++ b/package/gnupg/gnupg.mk
@@ -11,7 +11,12 @@ GNUPG_LICENSE = GPL-3.0+
 GNUPG_LICENSE_FILES = COPYING
 GNUPG_DEPENDENCIES = zlib ncurses $(if $(BR2_PACKAGE_LIBICONV),libiconv)
 GNUPG_CONF_ENV = ac_cv_sys_symbol_underscore=no
-GNUPG_CONF_OPTS = --disable-rpath --enable-minimal --disable-regex
+GNUPG_CONF_OPTS = \
+	--disable-rpath \
+	--enable-minimal \
+	--disable-regex \
+	--enable-sha256 \
+	--enable-sha512
 
 # gnupg doesn't support assembly for coldfire
 ifeq ($(BR2_m68k_cf),y)
-- 
2.11.0 (Apple Git-81)

  parent reply	other threads:[~2017-04-07  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  1:09 [Buildroot] [PATCH 1/1] gnupg: Add options for SHA-256 and SHA-512 hashes Jack Breese
2017-04-06  4:01 ` Baruch Siach
2017-04-07  0:44   ` Jack Breese
2017-04-07  1:09 ` Jack Breese [this message]
2017-04-08 13:32   ` [Buildroot] [PATCH v2] " 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=20170407010943.80192-1-jack@kumunetworks.com \
    --to=jack@kumunetworks.com \
    --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.