Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!usc!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re:  bug in gcc 1.37.4 and XV11R4
Message-ID: <9008271127.AA08786@Larry.McRCIM.McGill.EDU>
Date: 27 Aug 90 11:27:49 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 23

> i tracked part of the problem down to sunInit.c and some ioctl()
> calls.  these calls were not working.  i recompiled sunInit.c with
> Sun cc and the ioctl() calls succeded.

> i've tried the compiles with gcc before and after running the
> fixincludes script.

Are you certain fixincludes actually worked?  Try a simple test:

#include <sys/ioctl.h>
SIOCGIFCONF

Run that through cc -E and gcc -E and compare the last line of output.
They should be (functionally) identical.  If they're not, your gcc
include files are broken, regardless of what you have or haven't run,
and you'll have to find/fix that problem before you have much hope of
getting Xsun's ioctls to compile correctly with gcc.  (Typical symptom:
gcc output has 'x' where cc output has 'i'.)

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu