kaleb@mars.jpl.nasa.gov (Kaleb Keithley) (01/05/90)
1. We had X11R3 working fine yesterday.
2. We compiled everything in R4 with gnu 1.36 except rgb which we compiled
with cc.
3. We are on a Sun 4/260 running 4.0.3
4. We start the server with xinit, exactly the same as with R3. After about
three seconds the server prints the following and dies:
Getting interface configuration: Operation not supported on socket
sunOpenFrameBuffer: Inappropriate ioctl for device
Fatal server bug!
no screens found
XIO: fatal IO error 32 (Broken pipe) on X server "(null)"
after 0 requests (0 known processed) with 0 events remaining.
The connection was probably broken by a server shutdown or KillClient.
We looked at where the error is being generated (access.c) and it appears that
it is attempting to use TCP sockets rather than UNIX domain sockets. Why?
server/os/4.2bsd was compiled with both -DTCPCONN and -DUNIXCONN.
Thanks in advance.
Chewey, get us outta here!
kaleb@mars.jpl.nasa.gov (818)354-8771
Kaleb Keithleykaleb@mars.jpl.nasa.gov (Kaleb Keithley) (01/05/90)
In article <2511@jato.Jpl.Nasa.Gov> (Kaleb Keithley) writes: >1. We had X11R3 working fine yesterday. >2. We compiled everything in R4 with gnu 1.36 except rgb which we compiled >with cc. >3. We are on a Sun 4/260 running 4.0.3 >4. We start the server with xinit, exactly the same as with R3. After about >three seconds the server prints the following and dies: > >Getting interface configuration: Operation not supported on socket >sunOpenFrameBuffer: Inappropriate ioctl for device > >Fatal server bug! >no screens found >XIO: fatal IO error 32 (Broken pipe) on X server "(null)" > after 0 requests (0 known processed) with 0 events remaining. > The connection was probably broken by a server shutdown or KillClient. We just recompiled with cc and the server now works. Is this similar to R3 where oscolor.c had to be compiled with cc, while everything else could be compiled with gcc? Rather than try one file at a time with gcc, perhaps the good folks at expo already know what the one file is? again, thanks in advance. Chewey, get us outta here! kaleb@mars.jpl.nasa.gov (818)354-8771 Kaleb Keithley
keith@EXPO.LCS.MIT.EDU (Keith Packard) (01/05/90)
Sounds like you haven't used the gcc shell script 'fixincludes' which whacks the system header files to make them work with an ansi compiler. When building R3, most people used -traditional for the server; R4 no longer needs that flag, except for the system header files (which use a rather broken mechanism to specify the arguments to ioctl). Run fixincludes and rebuild server/ddx/sun, lib/X, clients/xterm and any other portion you built with gcc and which uses ioctl. Good luck! Keith Packard MIT X Consortium