From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: crypt mismatch
Date: Fri, 19 Feb 2016 11:55:00 -0000 [thread overview]
Message-ID: <20160219115513.GB8295@calimero.vinschen.de> (raw)
In-Reply-To: <56C65601.2030702@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Feb 19 00:38, Marco Atzeri wrote:
> on x86:
>
> $ cygcheck -f /usr/bin/cygcrypt-0.dll
> crypt-1.2-1
>
> $ cygcheck -l crypt
> /usr/bin/cygcrypt-0.dll
> /usr/bin/crypt.exe
> /usr/lib/libcrypt.a
> /usr/lib/libcrypt.dll.a
> /usr/include/crypt.h
> /usr/share/doc/Cygwin/crypt.README
>
>
> on x64
>
> crypt 1.1-1
> libcrypt-devel 1.1-1
> libcrypt0 1.1-1
That's ok. Crypt 1.2-1 for 32 bit is older than crypt 1.1-1 for 64 bit.
I could create a new 1.3-1 for both but... meh.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-19 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160218231017.42741.qmail@sourceware.org>
2016-02-18 23:38 ` Marco Atzeri
2016-02-19 11:55 ` Corinna Vinschen [this message]
2016-03-17 22:02 ` Yaakov Selkowitz
2016-03-18 10:12 ` Corinna Vinschen
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=20160219115513.GB8295@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).