From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Libssl 1.0 corrupted after upgrading from 2.10 to 3.x latest
Date: Thu, 18 Apr 2019 05:45:00 -0000 [thread overview]
Message-ID: <e91db805-e7ea-4e2c-680c-4ccb89e77986@SystematicSw.ab.ca> (raw)
In-Reply-To: <6EBACC87-CEB6-4AFD-9446-05466292533D@financialengines.com>
On 2019-04-17 17:39, Sudheer Kolli wrote:
> We got an issue where we were unable to run curl or lftp and throwing error
> with cygssl_1.0.0.dll. So upgraded the Cygwin to latest version and I am
> using chocolatey installer in windows. After that also I see packages are
> still pointing to old ssl.
>
> The following are errors when I ssh into that windows box and try to run the
> program.
> C:/opt/cygwin64/bin/curl.exe: error while loading shared libraries: ?:
> cannot open shared object file: No such file or directory
> C:/opt/cygwin64/bin/lftp.exe: error while loading shared libraries:
> cygssl-1.0.0.dll: cannot open shared object file: No such file or directory
>
> Any help would be appreciated.
Try de-/re-installing the problem packages using Cygwin setup, and allow
dependent libraries to also be de-/re-installed.
--
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.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-04-18 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 23:39 Sudheer Kolli
2019-04-18 5:45 ` Brian Inglis [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=e91db805-e7ea-4e2c-680c-4ccb89e77986@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).