Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!rutgers!usc!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re:  HELP! constype always reports "tty" on SUN console (R4)
Message-ID: <9003110957.AA23354@Larry.McRCIM.McGill.EDU>
Date: 11 Mar 90 09:57:16 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 35

> Hello, could anyone help me ?

> I installed V11R4 on our Sun 3/260 including fixes 1 and 2 for the
> core.  When I want to run xinit I always get Error messages like
> this:

> Getting interface configuration: Operation not supported on socket
> sunOpenFrameBuffer: Inappropriate ioctl for device
> sunOpenFrameBuffer: Inappropriate ioctl for device
> sunOpenFrameBuffer: Inappropriate ioctl for device
> sunOpenFrameBuffer: Inappropriate ioctl for device
> sunOpenFrameBuffer: Inappropriate ioctl for device

> Whats wrong ?

You don't say enough to be sure, but here's my guess:  you built the
server with gcc 1.37.  Gcc 1.37 has a broken fixincludes script (or so
I'm told by the person who maintains gcc here), and as a result all
ioctls pass the wrong value to the kernel.  Here's a quick experiment
to see whether this is the problem: Put this in a file, say x.c:

#include <sys/ioctl.h>
main(){foo(SIOCGIFCONF);}

Now run "cc -E x.c | tail -1" and "gcc -E x.c | tail -1".  They should
produce essentially the same output (whitespace differences can be
ignored).  If the gcc output has 'x' where the cc output has some other
letter in quotes ('i', I think it should be), your gcc's fixincludes
script is broken (or wasn't run, or wasn't run correctly, or the gcc
include files have been trashed, or something of the sort).

					der Mouse

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