irf@kuling.UUCP (09/23/87)
Somehow my previous article read the wrong file and not the one with my comments on the 'termio.c' source code. The parts that my Sys V.2 can't digest is the 'V7' block where struct tchars ... and struct ltchars ... are specified. 'tchars' and 'ltchars' are not understood by SysV.2. Furthermore, the 'V7' block with 'gtty' for saving old state and definig a new state etc is completely unitelligible. Things like TIOCGETC mach my 'cc' get the hickups.. The rest will probably work but I'm not sure, since my 'cc' dies with the message "Too many errors..." ---------------------------- Swedish Institute of Space Physics, Uppsala, Sweden
davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr) (10/13/87)
In article <490@kuling.UUCP> irf@kuling.UUCP (Stellan Bergman) writes: |Somehow my previous article read the wrong file and not the one |with my comments on the 'termio.c' source code. The parts that |my Sys V.2 can't digest is the 'V7' block where struct tchars ... I have compiled uemacs on the following SysV based systems without problems: UNICOS (Cray2), Xenix (AT), Release 3.0 and 3.5 for AT&T unix-pc (68010 based), Microport UNIX (AT), and Simultask (AT&T 6300+). I seriously believe that either you didn't configure the header file correctly or that your UNIX is broken. I don't think you will find anyone to send you "a working version of the code." Most of these machines have gone from 3.7i -> 3.if -> 3.8i -> 3.9, although some have skipped versions. Hope this helps you identify the problem. -- bill davidsen (wedu@ge-crd.arpa) {uunet | philabs | seismo}!steinmetz!crdos1!davidsen "Stupidity, like virtue, is its own reward" -me
irf@kuling.UUCP (Stellan Bergman) (10/18/87)
In article <7615@steinmetz.steinmetz.UUCP> davidsen@crdos1.UUCP (bill davidsen) writes: >I have compiled uemacs on the following SysV based systems without >problems: UNICOS (Cray2), Xenix (AT), Release 3.0 and 3.5 for AT&T >unix-pc (68010 based), Microport UNIX (AT), and Simultask (AT&T 6300+). > >I seriously believe that either you didn't configure the header file >correctly or that your UNIX is broken. I don't think you will find >... I have found the reason: We had uemacs 2.0 and apparently that version was never intended to work in SysV.2. Several people have told me that uemacs 3.7 (and later versions) do work and there is even people who are kind enough to offer me a copy that works on the same machines (HP9000 series) that we have. It's still in the mail, though... (By the way we never got our uemacs 2.0 to compile properly on an IBM/PC clone even though we tried several different C compilers...) Thank you for all info (and encouragement) Newsgroups: comp.unix.questions Subject: Re: Does uemacs really work ins SysV.2? Summary: Expires: References: <490@kuling.UUCP> <7615@steinmetz.steinmetz.UUCP> Sender: Reply-To: irf@kuling.UUCP (Stellan Bergman) Followup-To: Distribution: Organization: Dept. of Computer Systems, Uppsala University, Sweden Keywords: In article <7615@steinmetz.steinmetz.UUCP> davidsen@crdos1.UUCP (bill davidsen) writes: >In article <490@kuling.UUCP> irf@kuling.UUCP (Stellan Bergman) writes: >|Somehow my previous article read the wrong file and not the one >|with my comments on the 'termio.c' source code. The parts that >|my Sys V.2 can't digest is the 'V7' block where struct tchars ... > >I have compiled uemacs on the following SysV based systems without >problems: UNICOS (Cray2), Xenix (AT), Release 3.0 and 3.5 for AT&T >unix-pc (68010 based), Microport UNIX (AT), and Simultask (AT&T 6300+). > >I seriously believe that either you didn't configure the header file >correctly or that your UNIX is broken. I don't think you will find >anyone to send you "a working version of the code." Most of these >machines have gone from 3.7i -> 3.if -> 3.8i -> 3.9, although some have >skipped versions. > >Hope this helps you identify the problem. >-- > bill davidsen (wedu@ge-crd.arpa) > {uunet | philabs | seismo}!steinmetz!crdos1!davidsen >"Stupidity, like virtue, is its own reward" -me Newsgroups: comp.unix.questions Subject: Re: Does uemacs really work ins SysV.2? Summary: Expires: References: <490@kuling.UUCP> <7615@steinmetz.steinmetz.UUCP> Sender: Reply-To: irf@kuling.UUCP (Stellan Bergman) Followup-To: Distribution: Organization: Dept. of Computer Systems, Uppsala University, Sweden Keywords: In article <7615@steinmetz.steinmetz.UUCP> davidsen@crdos1.UUCP (bill davidsen) writes: >In article <490@kuling.UUCP> irf@kuling.UUCP (Stellan Bergman) writes: >|Somehow my previous article read the wrong file and not the one >|with my comments on the 'termio.c' source code. The parts that >|my Sys V.2 can't digest is the 'V7' block where struct tchars ... > >I have compiled uemacs on the following SysV based systems without >problems: UNICOS (Cray2), Xenix (AT), Release 3.0 and 3.5 for AT&T >unix-pc (68010 based), Microport UNIX (AT), and Simultask (AT&T 6300+). > >I seriously believe that either you didn't configure the header file >correctly or that your UNIX is broken. I don't think you will find >... I have found the reason: We had uemacs 2.0 and apparently that version was never intended to work in SysV.2. Several people have told me that uemacs 3.7 (and later versions) do work and there is even people who are kind enough to offer me a copy that works on the same machines (HP9000 series) that we have. It's still in the mail, though... Thank you for all info (and encouragement)