From: Eliot Moss <moss@cs.umass.edu>
To: Keith Christian <keith1christian@gmail.com>, cygwin@cygwin.com
Cc: jaltman@secure-endpoints.com
Subject: Re: Compiling C-Kermit 9.0.305 Alpha.02 on Cygwin
Date: Mon, 30 Nov 2020 17:31:46 -0500 [thread overview]
Message-ID: <c662458a-f989-f1ee-83cc-04f0c9a6548e@cs.umass.edu> (raw)
In-Reply-To: <CAFWoy7EXg_eDieymas3jKrYSxKr+nD9CqP3f6MKPMALc0aAaxw@mail.gmail.com>
On 11/30/2020 5:17 PM, Keith Christian via Cygwin wrote:
> On Mon, Nov 30, 2020 at 2:44 PM Jeffrey Altman
> <jaltman@secure-endpoints.com> wrote:
>> 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
>
> Jeffrey,
>
> Thanks so much, appreciate your taking the time to respond. I was
> puzzled when C-Kermit was dropped from Cygwin several years ago.
> Former Kermit developer, quite the credentials!
Just checked, and this does not compile out of the box for either the linux or posix target. Not
sure how much work will be required. Too bad it is not set up to use ./configure to see what's
actually available on the platform / how to use it ...
Best wishes - Eliot Moss
next prev parent reply other threads:[~2020-11-30 22:31 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
2020-11-30 22:17 ` Keith Christian
2020-11-30 22:31 ` Eliot Moss [this message]
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=c662458a-f989-f1ee-83cc-04f0c9a6548e@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=jaltman@secure-endpoints.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).