public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mario Emmenlauer <mario@emmenlauer.de>
To: cygwin@cygwin.com
Subject: Kind request to update 'nasm'
Date: Tue, 3 Jan 2023 22:33:14 +0100	[thread overview]
Message-ID: <6cb9660a-1273-1790-4cee-c445597d1798@emmenlauer.de> (raw)


Dear All,

the current version of OpenSSL (1.1.1s) fails to build for me with
an error in nasm. The issue is reported upstream and supposedly fixed
already, see https://bugzilla.nasm.us/show_bug.cgi?id=3392658

I've tested nasm 2.16.1 from the upstream win32 builds and it does
indeed fix the problem. However I would prefer a Cygwin deployment
over manually maintained archives.

Could someone kindly consider updating 'nasm' to current latest 2.16,
or anything including or higher than 2.15.01?

All the best,

     Mario Emmenlauer


--
BioDataAnalysis GmbH, Mario Emmenlauer      Tel. Buero: +49-89-74677203
Balanstr. 43                   mailto: memmenlauer * biodataanalysis.de
D-81669 München                          http://www.biodataanalysis.de/

                 reply	other threads:[~2023-01-03 21:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6cb9660a-1273-1790-4cee-c445597d1798@emmenlauer.de \
    --to=mario@emmenlauer.de \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).