From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: libfido2’s dependency on libcbor is dropped in setup.ini
Date: Wed, 17 Nov 2021 15:26:16 +0100 [thread overview]
Message-ID: <YZURCDxxvvoU1FWC@calimero.vinschen.de> (raw)
In-Reply-To: <D0DA8318-523D-4288-83F2-A3E490D5BEEB@gmail.com>
On Nov 17 11:57, ggl329 via Cygwin wrote:
> cygfido2-1.dll (from libfido2-1.9.0-1) depends on cygcbor-0.8.dll .
> But the dependency is dropped in setup.ini (depends2 field).
> In addition, the current libcbor-0.9.0-2 doesn’t provide cygcbor-0.8.dll but cygcbor-0.9.dll .
> Maybe, libfido2 needs to be rebuilt with libcbor-0.9 .
libcbor is closely knit to libfido2 and there's fortunately no other
package in the distro yet relying on libcbor.
Given that the 0.X releases are not binary compatible with each other
(which hopefully changes with the 1.X releases), I will change libcbor
to a static library only for the time being, and rebuild libfido2
against that static lib.
Thanks,
Corinna
prev parent reply other threads:[~2021-11-17 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 2:57 ggl329
2021-11-17 14:26 ` Corinna Vinschen [this message]
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=YZURCDxxvvoU1FWC@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).