[comp.windows.x] X11R4 on sun 4/110

nesman@inmet.inmet.com (08/02/90)

>I have recently compiled X11R4 on a Sun 4-110. Everthing appeared
>to  go  very well until I came to run the server. Xinit starts it
>up o.k. but the mouse will only respond to one motion  event  be-
>fore  it  seizes  up. Applications can be started and stoped from
>other terminals without any problems, but a  focused  xterm  does
>not  seem  to  receive any keyboard events. After a number of key
>presses an error message pops up in the console xterm
>
>         "kbdqueueevent: can't allocate block for event".
>
>When the focused window is killed off another message appears
>
>         "newmsg : out of blocks".
		.
		.
		.
>                Simon Turner    ( I'll think of a signature later )
>
>Tetra Ltd.  Concord Road Maidenhead Berks. SL6 4BX.

I found that the server would not run correctly (with the above symptoms)
when compiled with /usr/5bin/cc (which uses /usr/5lib for C libraries).
When compiled with /usr/bin/cc every thing was fine.

Stephen Nesman
Intermetrics Inc.
nesman@inmet.inmet.com		uunet!inmet!nesman

guy@auspex.auspex.com (Guy Harris) (08/05/90)

>I found that the server would not run correctly (with the above symptoms)
>when compiled with /usr/5bin/cc (which uses /usr/5lib for C libraries).
>When compiled with /usr/bin/cc every thing was fine.

Yup, if "/usr/bin/cc" and "/usr/5bin/cc" produced code that worked the
same, Sun wouldn't have provided both of them.  X11 for Suns probably
shares lots of code written assuming BSD-style behavior, and as such
should be compiled in the environment that provides that behavior, i.e.
compiled with "/usr/bin/cc".

Why that causes streams buffers to be eaten up (which is what the
messages in question indicate happened) is another matter; perhaps the
miscompiled X server is misbehaving and not reading from the keyboard or
mouse file descriptors, and various flow control limits aren't set
appropriately to keep the system from running out of streams buffers in
that situation.