From: Jeffrey Altman <jaltman@secure-endpoints.com>
To: Keith Christian <keith1christian@gmail.com>, cygwin@cygwin.com
Subject: Re: Compiling C-Kermit 9.0.305 Alpha.02 on Cygwin
Date: Mon, 30 Nov 2020 16:44:10 -0500 [thread overview]
Message-ID: <06e96083-6a33-2cbb-a829-455615e91df7@secure-endpoints.com> (raw)
In-Reply-To: <CAFWoy7Hr5VXmztz-7pEKCNPLuOZpnW0srZB-FSs_EJDLEXbfEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On 11/30/2020 10:06 AM, Keith Christian via Cygwin (cygwin@cygwin.com)
wrote:
> I downloaded the .tar.gz of C-Kermit 9.0.305 Alpha.02, 19 September 2020.
> Web page: http://www.kermitproject.org/ckdaily.html
> Source download: http://www.kermitproject.org/ftp/kermit/test/tar/x.tar.gz
>
> I realize that C-Kermit has not been in the Cygwin distribution for
> awhile. There is no "cygwin" target in the makefile in the x.tar.gz
> source distribution.
> Is there any guidance for how to compile this modern version of
> C-Kermit for present-day Cygwin?
>
> Thanks.
I suspect building C-Kermit with SSH, OpenSSL, Kerberos v5 support is
going to be problematic since none of that code has been updated in more
than a decade to keep up with the latest upstream packages. I suggest
you start by trying to build for a generic linux target without any
security features.
Jeffrey Altman
former Kermit developer
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4080 bytes --]
next prev parent reply other threads:[~2020-11-30 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 15:06 Keith Christian
2020-11-30 18:23 ` Achim Gratz
2020-11-30 21:44 ` Jeffrey Altman [this message]
2020-11-30 22:17 ` Keith Christian
2020-11-30 22:31 ` Eliot Moss
2020-11-30 23:15 ` Keith Christian
2020-12-01 4:21 ` gs-cygwin.com
2020-12-01 16:20 ` Keith Christian
2020-12-01 17:32 ` gs-cygwin.com
2020-12-01 22:09 ` Keith Christian
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=06e96083-6a33-2cbb-a829-455615e91df7@secure-endpoints.com \
--to=jaltman@secure-endpoints.com \
--cc=cygwin@cygwin.com \
--cc=keith1christian@gmail.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).