> Should the "#include " in telnet.c be protected with a
> "#ifdef TERMCAP"?
Dunno. I have removed it from 2 builds - one clean and one with all
my crypto gunk (both failed, BTW). One box will take 1.5 hours, the
other will take 3.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.o
> > > invalid use of undefined type `struct termio'
> >
> > I suspect it's related to the international secure dist being out of sync.
> > Make sure there's no -DTERMCAP in the telnet Makefiles...
>
> Nope. The makefiles are in src/kerberosIV/... and they are not
> export restricted.
Well I'm n
> > invalid use of undefined type `struct termio'
>
> I suspect it's related to the international secure dist being out of sync.
> Make sure there's no -DTERMCAP in the telnet Makefiles...
Nope. The makefiles are in src/kerberosIV/... and they are not
export restricted.
M
--
Mark Murray
Join th
> invalid use of undefined type `struct termio'
> /usr/src/kerberosIV/usr.bin/telnet/../../../crypto/telnet/telnet/telnet.c:2065:
> invalid use of undefined type `struct termio'
> /usr/src/kerberosIV/usr.bin/telnet/../../../crypto/telnet/telnet/telnet.c:2120:
I'm so glad you said this! I though
John Hay wrote:
> A "make release" on -current also breaks there. It looks like it might be
> related to the new ncurses import, because it complains about:
>
> invalid use of undefined type `struct termio'
I suspect it's related to the international secure dist being out of sync.
Make sure ther
A "make release" on -current also breaks there. It looks like it might be
related to the new ncurses import, because it complains about:
invalid use of undefined type `struct termio'
John
--
John Hay -- [EMAIL PROTECTED]
> Partway through a make world, I'm seeing the following, I've applied up