From: gs-cygwin.com@gluelogic.com
To: Keith Christian <keith1christian@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Compiling C-Kermit 9.0.305 Alpha.02 on Cygwin
Date: Tue, 1 Dec 2020 12:32:35 -0500 [thread overview]
Message-ID: <20201201173235.GA47925@xps13> (raw)
In-Reply-To: <CAFWoy7FzniOvOoxJ7WM+G2U3EW92kQOU=k2T68hPRsNeTL5Z9A@mail.gmail.com>
On Tue, Dec 01, 2020 at 09:20:51AM -0700, Keith Christian wrote:
> On Mon, Nov 30, 2020 at 9:23 PM <gs-cygwin.com@gluelogic.com> wrote:
> > For kicks, I got the *basic* C-Kermit to build under Linux and under Cygwin.
> > https://github.com/gstrauss/ckermit
> > The make command line options are in the commit messages.
> >
> > It is based on
> > http://www.columbia.edu/kermit/archive.html
> > C-Kermit 9.0.302 2011/07/11 cku302.tar.gz
> >
> > I realized afterwards that I should have used C-Kermit 9.0.305 Alpha.02.
> >
> > In any case, compiling is a first step, but does not suggest it is fully
> > functional. Mostly #include and minor changes were needed, except for
> > one big mess with the cygwin custom struct hostent being defined with
> > const char *h_name
> >
> > Cheers, Glenn
>
> Glenn,
>
> I tried "make linux" this morning on the 9.0.305 version, got this
> output, (I_am_not_expecting_any_assistance_,) more of a report:
>
> -rw-r-----+ 1 keith keith 382913 Sep 19 14:17 makefile
>
> CYGWIN_NT-10.0 DESKTOP-OLN71TE 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin
>
> 1 Making C-Kermit for Linux...
> 2 /bin/sh: line 68: -f: command not found
> 3 make[1]: Entering directory 'kermit_downloads/kermitsource'
> 4 Making C-Kermit "9.0.305" for Linux 1.2 or later...
> 5 IMPORTANT: Read the comments in the linux section of the
> 6 makefile if you have trouble.
> 7 make xermit KTARGET=${KTARGET:-linuxa} "CC = gcc" "CC2 = gcc" \
> 8 "CFLAGS = -O -DLINUX -pipe -funsigned-char -DFNFLOAT -DCK_POSIX_SIG \
> 9 -DCK_NEWTERM -DTCPSOCKET -DLINUXFSSTND -DNOCOTFMC -DPOSIX \
> 10 -DUSE_STRERROR -DCK_NCURSES -I/usr/include/ncurses
> -DHAVE_CRYPT_H -DHAVE_OPENPTY " "LNKFLAGS = " \
> 11 "LIBS = -lutil -lncurses -lresolv -lcrypt -lm"
> 12 make[2]: Entering directory 'kermit_downloads/kermitsource'
> 13 gcc -O -DLINUX -pipe -funsigned-char -DFNFLOAT -DCK_POSIX_SIG
> -DCK_NEWTERM -DTCPSOCKET -DLINUXFSSTND -DNOCOTFMC -DPOSIX
> -DUSE_STRERROR -DCK_NCURSES -I/usr/include/ncurses -DHAVE_CRYPT_H
> -DHAVE_OPENPTY -DKTARGET=\"linux\" -c ckucmd.c
> 14 ckucmd.c: In function ‘cmdconchk’:
> 15 ckucmd.c:7579:22: error: ‘__FILE’ has no member named ‘_IO_read_end’
> 16 7579 | x = (int) ((stdin->_IO_read_end) - (stdin->_IO_read_ptr));
> 17 | ^~
> 18 ckucmd.c:7579:46: error: ‘__FILE’ has no member named ‘_IO_read_ptr’
> 19 7579 | x = (int) ((stdin->_IO_read_end) - (stdin->_IO_read_ptr));
> 20 | ^~
> 21 make[2]: *** [makefile:988: ckucmd.o] Error 1
> 22 make[2]: Leaving directory 'kermit_downloads/kermitsource'
> 23 make[1]: *** [makefile:6067: linuxa] Error 2
> 24 make[1]: Leaving directory 'kermit_downloads/kermitsource'
> 25 make: *** [makefile:6100: linux] Error 2
>
> Only two .o files were created:
>
> -rw-r--r--+ 1 keith keith 48034 Dec 1 08:55 ckcmai.o
> -rw-r--r--+ 1 keith keith 37108 Dec 1 08:55 ckclib.o
>
> Keith
Keith, kindly look at the commits in
https://github.com/gstrauss/ckermit
https://github.com/gstrauss/ckermit/commits/master
> output, (I_am_not_expecting_any_assistance_,) more of a report:
Why bother posting before taking half a second to look at the commits?
next prev parent reply other threads:[~2020-12-01 17:32 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
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 [this message]
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=20201201173235.GA47925@xps13 \
--to=gs-cygwin.com@gluelogic.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).