mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Alexander Aring <alex.aring@gmail.com>
Subject: [ptxdist] [PATCH 0/4] zeromq: version bump
Date: Fri,  8 Jul 2022 09:10:58 +0200	[thread overview]
Message-ID: <20220708071102.18393-1-ada@thorsis.com> (raw)

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




             reply	other threads:[~2022-07-08  7:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  7:10 Alexander Dahl [this message]
2022-07-08  7:10 ` [ptxdist] [PATCH 1/4] libzmq: Pin some more configure options Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-08  7:11 ` [ptxdist] [PATCH 2/4] libzmq: Revise license and add license file hashes Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-08  7:11 ` [ptxdist] [PATCH 3/4] libzmq: version bump 4.0.4 -> 4.3.4 Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-08  7:11 ` [ptxdist] [PATCH 4/4] libzmq: Prefer external libsodium over internal tweetnacl Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-08  9:26 ` [ptxdist] [PATCH 0/4] zeromq: version bump Michael Olbrich
2022-07-08 15:15 ` Michael Olbrich

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=20220708071102.18393-1-ada@thorsis.com \
    --to=ada@thorsis.com \
    --cc=alex.aring@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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