From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 08 Jul 2022 09:12:09 +0200 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1o9i9m-00ADhq-BB for lore@lore.pengutronix.de; Fri, 08 Jul 2022 09:12:09 +0200 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1o9i9o-0002ZS-Jb; Fri, 08 Jul 2022 09:12:08 +0200 Received: from mail.thorsis.com ([92.198.35.195]) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1o9i8l-0001uS-Bz for ptxdist@pengutronix.de; Fri, 08 Jul 2022 09:11:07 +0200 Received: from adahl by ada.ifak-system.com with local (Exim 4.92) (envelope-from ) id 1o9i8k-0004nX-Bx; Fri, 08 Jul 2022 09:11:02 +0200 From: Alexander Dahl To: ptxdist@pengutronix.de Date: Fri, 8 Jul 2022 09:10:58 +0200 Message-Id: <20220708071102.18393-1-ada@thorsis.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: [ptxdist] [PATCH 0/4] zeromq: version bump X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Cc: Alexander Aring Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false Hello, for a proprietary SDK in on of our BSPs we need a recent version of zeromq, so I took the opportunity to upgrade it. The first three patches should be straight forward, although a lot of new configure options were introduced. The fourth patch switches from embedded tweetnacl to external libsodium, which I sent for a version bump series yesterday. I'm not 100% sure about that change, anyone with a better understanding of security implications might veto that patch. One thing more: buildroot sets some autoconf cache variables [1] which are reported in zeromq prepare step (configure) like this: checking whether EFD_CLOEXEC is supported... not during cross-compile … checking whether SOCK_CLOEXEC is supported... not during cross-compile checking whether O_CLOEXEC is supported... not during cross-compile checking whether SO_BINDTODEVICE is supported... not during cross-compile checking whether SO_KEEPALIVE is supported... not during cross-compile checking whether TCP_KEEPCNT is supported... not during cross-compile checking whether TCP_KEEPIDLE is supported... not during cross-compile checking whether TCP_KEEPINTVL is supported... not during cross-compile checking whether TCP_KEEPALIVE is supported... not during cross-compile checking whether SO_PRIORITY is supported... not during cross-compile checking whether getrandom is supported... not during cross-compile Not sure if this should be taken care of by ptxdist's receipe, too? It could be added in a separate patch then. Greets Alex [1] https://git.busybox.net/buildroot/tree/package/zeromq/zeromq.mk Alexander Dahl (4): libzmq: Pin some more configure options libzmq: Revise license and add license file hashes libzmq: version bump 4.0.4 -> 4.3.4 libzmq: Prefer external libsodium over internal tweetnacl rules/libzmq.in | 1 + rules/libzmq.make | 41 ++++++++++++++++++++++++++++++++++------- 2 files changed, 35 insertions(+), 7 deletions(-) base-commit: 7384b37919cb66e12ff15b4264325cb5eba911c3 -- 2.30.2