From: igoresha@iwmail.com
To: cygwin@sourceware.cygnus.com
Cc: Sergey Okhapkin <sos@prospect.com.ru>
Subject: ssh 1.2.27 and 2.0.13 for b20.1: missed _ctype_ in cygwin1.dll
Date: Fri, 13 Aug 1999 05:28:00 -0000 [thread overview]
Message-ID: <990813081747L6.09501@webb3.iname.net> (raw)
Hello!
When I tried to use precompiled binaries for
ssh 1.2.27 and 2.0.13 under my b20.1 installation,
they failed to run due to:
The procedure entry point _ctype_ could not
be located in the dynamic link library cygwin1.dll
How can I fix this?
Regards, Igor Boukanov
-----------------------------------------------------
Get free email from CMP at http://www.cmpnetmail.com/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: igoresha@iwmail.com
To: cygwin@sourceware.cygnus.com
Cc: Sergey Okhapkin <sos@prospect.com.ru>
Subject: ssh 1.2.27 and 2.0.13 for b20.1: missed _ctype_ in cygwin1.dll
Date: Tue, 31 Aug 1999 23:49:00 -0000 [thread overview]
Message-ID: <990813081747L6.09501@webb3.iname.net> (raw)
Message-ID: <19990831234900.7dzTkkgy-9AmKghQ_DoCZatYp8yOaZ0YPz9jN71dPks@z> (raw)
Hello!
When I tried to use precompiled binaries for
ssh 1.2.27 and 2.0.13 under my b20.1 installation,
they failed to run due to:
The procedure entry point _ctype_ could not
be located in the dynamic link library cygwin1.dll
How can I fix this?
Regards, Igor Boukanov
-----------------------------------------------------
Get free email from CMP at http://www.cmpnetmail.com/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-08-13 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-13 5:28 igoresha [this message]
1999-08-31 23:49 ` igoresha
1999-08-13 5:37 Sergey Okhapkin
1999-08-31 23:49 ` Sergey Okhapkin
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=990813081747L6.09501@webb3.iname.net \
--to=igoresha@iwmail.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=sos@prospect.com.ru \
/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).