Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!mips!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!mathisen
From: mathisen@dali.cs.montana.edu (Jaye Mathisen)
Newsgroups: comp.unix.ultrix
Subject: Re: Ultrix3.1 bug in ioctl(2)?
Message-ID: <2038@dali>
Date: 4 Jun 90 15:16:52 GMT
References: <12035@shlump.nac.dec.com> <1772@tuegate.tue.nl>
Reply-To: mathisen@dali.UUCP (Jaye Mathisen)
Organization: Montana State University, Dept. of Computer Science, Bozeman MT 59717
Lines: 25

In article <1772@tuegate.tue.nl> rcpt@tuegate.tue.nl (Piet Tutelaers) writes:
>pilmeyer@utrtsc.dec.com (Han Pilmeyer) writes:
>>I've ran the noecho program (compiled with -DULTRIX_BUG) on several ULTRIX
>>systems. ULTRIX versions include V3.0 and V3.1 on both VAX and RISC.
>
>>I'm not getting error messages, and there is no echo for what I type.
>
>The bug I have reported is because I used gcc (version 1.36), without
>verifying, I supposed that the bug would also exist in native Ultrix
>
>Perhaps the error should be reported elsewhere?


The installation instructions for gcc mention that you need to run the
fixincludes script supplied with gcc to patch up the ioctl.h header
file.


I think you can also use the -traditional flag to gcc and it will work.
or use the system supplied C preprocessor, and let gcc at it after it's
been run through /usr/lib/cpp.



Anyway, tell your sysadmin to run fixincludes.