jbentley@PCS.CNC.EDU (jon bentley) (08/07/90)
Help! We are trying to compile X11 R4 on a SUN 3/280 serving five SUN 3/60's and when we run startx or xinit, here's what happens: The gray stipple comes up, A message comes up saying the following: Getting interface configuration: Operation not supported on socket xterm: Error 15, errno 25: Inappropriate ioctl for device waiting for X server to shut down Couldn't initialize translation to Event Then the regular prompt comes back up Our question is this; Is there a listing of error numbers and corresponding fixes for X? And, if so, where do you get this list? It's important that we get this running by this afternoon, so please RSVP!!!!!!!!!!! We're very new to X so any help anybody can give is very much appreciated. Thanks a bunch! jbentley Jon Bentley Student Assistant F. Hunter Creech Jr. Computer Lab Christopher Newport College Newport News, Virginia 23606
mouse@LARRY.MCRCIM.MCGILL.EDU (08/10/90)
> We are trying to compile X11 R4 on a SUN 3/280 serving five SUN > 3/60's and when we run startx or xinit, here's what happens: > The gray stipple comes up, > A message comes up saying the following: > Getting interface configuration: Operation not supported on socket > xterm: Error 15, errno 25: Inappropriate ioctl for device > waiting for X server to shut down > Couldn't initialize translation to Event > Then the regular prompt comes back up This looks remarkably like the symptom generated when gcc's fixincludes script was not run, was run incorrectly, was broken, etc. But what you say implies that the server is mostly alive and well. Did you build the server with cc and xterm with gcc? Did you perchance build part of the server with cc and part with gcc? If gcc was involved anywhere along the line, check your gcc include files. Create a little .c file somewhere with the following two lines in it #include <sys/ioctl.h> SIOCGIFCONF and run cc -E and gcc -E on it, and compare the last line of output betwen the two. They should be identical (except for whitespace differences). In particular, if the gcc output has something else (probably 'x') where the cc output has 'i', you need to fix your gcc include files before you have much hope of getting gcc to work for anything using ioctls. der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu