Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven.umd.edu!uvaarpa!murdoch!agate.cs.Virginia.EDU!acl3k
From: acl3k@agate.cs.Virginia.EDU (Allan Christian Long)
Newsgroups: comp.sys.sgi
Subject: Re: ioctl (Problem identified)
Keywords: IRIX, ioctl
Message-ID: <1991May24.200735.29625@murdoch.acc.Virginia.EDU>
Date: 24 May 91 20:07:35 GMT
Sender: usenet@murdoch.acc.Virginia.EDU
Reply-To: acl3k@agate.cs.Virginia.EDU (Allan Christian Long)
Organization: University of Virginia Computer Science Department
Lines: 18


	First, I'd like to thank everyone who replied to my postings
(via email and postings), as well as the people at SGI technical support.
I called them a couple times and everyone I talked to was very helpful.
	As a result of some source code an SGI engineer sent me,
I discovered that the problem was the compiler.  I was using GNU gcc,
which for some reason or another doesn't compile the ioctl FIONREAD
call correctly.  After recompiling that part of my code with the MIPS
cc compiler, the ioctl problem went away.  (Now I have another problem,
but that's a different story.  Has anybody ever connected a Polhemus
to an Iris?)
	I guess this goes to show you can't trust any piece of software.

- Chris


A. Chris Long, Jr.			acl3k@virginia.edu
If only we could overcome our tools...