Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] package/libnss: fix build warning
Date: Wed, 23 Oct 2019 12:23:28 +0200	[thread overview]
Message-ID: <20191023102330.20842-2-giulio.benetti@benettiengineering.com> (raw)
In-Reply-To: <20191023102330.20842-1-giulio.benetti@benettiengineering.com>

Add patch to fix build warning due to uninitialized variable.

Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
---
https://bugzilla.mozilla.org/show_bug.cgi?id=1590678
---
 ...ve-Wmaybe-uninitialized-warning-in-t.patch | 27 +++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 package/libnss/0004-Bug-1590678-Remove-Wmaybe-uninitialized-warning-in-t.patch

diff --git a/package/libnss/0004-Bug-1590678-Remove-Wmaybe-uninitialized-warning-in-t.patch b/package/libnss/0004-Bug-1590678-Remove-Wmaybe-uninitialized-warning-in-t.patch
new file mode 100644
index 0000000000..956abeb4a5
--- /dev/null
+++ b/package/libnss/0004-Bug-1590678-Remove-Wmaybe-uninitialized-warning-in-t.patch
@@ -0,0 +1,27 @@
+From 24bcc8860310149da1524dbf25f3bc77f6476b11 Mon Sep 17 00:00:00 2001
+From: Giulio Benetti <giulio.benetti@benettiengineering.com>
+Date: Wed, 23 Oct 2019 11:58:12 +0200
+Subject: [PATCH] Bug 1590678 - Remove -Wmaybe-uninitialized warning in
+ tls13esni.c
+
+Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
+---
+ nss/lib/ssl/tls13esni.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/nss/lib/ssl/tls13esni.c b/nss/lib/ssl/tls13esni.c
+index 4d2e12d62..a7ce6f568 100644
+--- a/nss/lib/ssl/tls13esni.c
++++ b/nss/lib/ssl/tls13esni.c
+@@ -728,7 +728,7 @@ tls13_ServerDecryptEsniXtn(const sslSocket *ss, const PRUint8 *in, unsigned int
+ {
+     sslReader rdr = SSL_READER(in, inLen);
+     PRUint64 suite;
+-    const ssl3CipherSuiteDef *suiteDef;
++    const ssl3CipherSuiteDef *suiteDef = NULL;
+     SSLAEADCipher aead = NULL;
+     TLSExtension *keyShareExtension;
+     TLS13KeyShareEntry *entry = NULL;
+-- 
+2.20.1
+
-- 
2.20.1

  reply	other threads:[~2019-10-23 10:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 10:23 [Buildroot] [PATCH 1/4] package/libnss: fix build failure with ARM without NEON extension Giulio Benetti
2019-10-23 10:23 ` Giulio Benetti [this message]
2019-10-24  8:47   ` [Buildroot] [PATCH 2/4] package/libnss: fix build warning Arnout Vandecappelle
2019-10-24  8:50     ` Arnout Vandecappelle
2019-10-24  8:51       ` Arnout Vandecappelle
2019-10-24 10:49         ` Giulio Benetti
2019-10-23 10:23 ` [Buildroot] [PATCH 3/4] package/libnss: remove useless NSS_ENABLE_ECC variable Giulio Benetti
2019-10-24  8:48   ` Arnout Vandecappelle
2019-10-23 10:23 ` [Buildroot] [PATCH 4/4] package/libnss: remove NSS_ENABLE_WERROR=0 Giulio Benetti
2019-10-23 15:54   ` Thomas Petazzoni
2019-10-23 16:10     ` Giulio Benetti
2019-10-23 21:44 ` [Buildroot] [PATCH 1/4] package/libnss: fix build failure with ARM without NEON extension Arnout Vandecappelle
2019-10-24 11:03   ` Giulio Benetti
2019-10-28 16:55   ` [Buildroot] [PATCH v2] " Giulio Benetti
2019-10-29 11:55     ` Giulio Benetti

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=20191023102330.20842-2-giulio.benetti@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox