From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: [ITA] libgcrypt
Date: Fri, 1 Apr 2022 18:41:29 -0600 [thread overview]
Message-ID: <d7c4af02-ac76-257d-80ad-fe13d5de6011@SystematicSw.ab.ca> (raw)
I'd like to offer to adopt maintenance of libgcrypt.
Updated playground cygport:
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/libgcrypt.git;a=blob;f=libgcrypt.cygport;hb=refs/heads/playground
Build based on patch from and similar options to Fedora 36/Rawhide/Main
(f36 chosen for longer availability), and also previous Cygwin release,
which enables asm modules only on 32 bit i686/x86, but disables asm
modules on 64 bit x86_64/amd64, as 22/33 test programs using asm modules
still SEGV there.
Scallywag build:
https://github.com/cygwin/scallywag/actions/runs/2076618935
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next reply other threads:[~2022-04-02 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 0:41 Brian Inglis [this message]
2022-04-02 15:14 ` Marco Atzeri
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=d7c4af02-ac76-257d-80ad-fe13d5de6011@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@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).