Mail Archives: cygwin-developers/1999/01/03/19:04:10
On Mon, Jan 04, 1999 at 03:45:56AM +0100, Corinna Vinschen wrote:
>Christopher Faylor wrote:
>> That's very strange. It almost sounds like some code from an experimental
>> branch leaked into the latest snapshot. I've been working, in my spare time,
>> on rewriting parts of fhandler_console.cc . The rewritten code does not
>> need that test so I've ifdef'ed it. I must have somehow copied this file
>> to the main trunk.
>
>Did I understand right, I should let it in state `#if 1'?
Actually, the #if shouldn't be there at all.
>> This is a termios.h problem. The termios struct changed recently.
>> cygwin1.dll detects when it is being used with an executable which
>> uses the older style termios struct and translates back and forth between
>> the new and old versions of the struct internally. If you link a program
>> with the new libcygwin.a then cygwin1.dll will assume that you are using the
>> new termios structure.
>>
>> In your case, it sounds like you're using a libncurses or libtermcap library
>> that was compiled a while ago and uses the old termios structure but you're
>> also using the newer libcygwin.a which contains a version number that will
>> tell cygwin1.dll to use the new style structs.
>>
>> The best solution is to recompile everything.
>
>After replacing sys/termios.h with the new version, everything seems to work
>fine. I've tested with tcsh.termcap, tcsh.ncurses and pdksh.
>
>Thank you for the hint, I forgot to replace this file.
Thanks for being an advanced tester for this stuff. I wish I could think of
some way to ensure fool-proff backwards compatibility.
>> It is beginning to sound like we should release a B21 very soon which breaks
>> binary compatibility with older versions of cygwin. The termios changes
>> were inavoidable but they may end up causing some problems.
>
>I agree (don't beat me: eventually with tape and raw device patch?).
Yes. Eventually... :-)
-chris
- Raw text -