Article View: gnu.emacs.bug
Article #79418.58 with X11 support under SCO ODT 2.0?
From: Jordan K Hubbard
Date: Thu, 01 Oct 1992 18:57
Date: Thu, 01 Oct 1992 18:57
15 lines
1321 bytes
1321 bytes
Not wanting to get too involved with this (I try to avoid even
standing close to the machine SCO's running on), I compiled 18.58
under SCO ODT 2.0 and noticed that X11 support was hosed - the old
dreaded "Xlib ... sequence lost" messages indicating that something
had gone wrong with I/O to the xlib connection socket. I've seen this
previously with other braindead SYSV machines trying to use SIGIO, and
taken the provided SIG_{UN}BLOCK fix, but this is more of a puzzler
since SCO doesn't even use SIGIO. Like I said, I didn't want to get
too involved with this (and so just compiled emacs without X support
for now), but I'd appreciate it if anyone has a fix for this that I
can just apply and forget that I ever logged into a SCO machine. Ugh!
I'm getting hives just thinking about the experience. Ik ik ik ik ik
ik.. Cooties! I touched it! I'm diseased!
Jordan
Technical Details
Message-ID:
<JKH.92Oct1145754@esel.lotus.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!convex!linac!pacific.mps.ohio-state.edu!cis.ohio-state.edu!esel.UUCP!jkhShow Full Headers
Complete Article Headers
Newsgroups: gnu.emacs.bug Path: arc1-ca.pugleaf.net!sparky!uunet!convex!linac!pacific.mps.ohio-state.edu!cis.ohio-state.edu!esel.UUCP!jkh From: jkh@esel.UUCP (Jordan K Hubbard) Subject: 18.58 with X11 support under SCO ODT 2.0? Message-ID: <JKH.92Oct1145754@esel.lotus.com> Sender: gnulists@ai.mit.edu Organization: Lotus Ireland Distribution: gnu Date: Thu, 1 Oct 1992 18:57:54 GMT Approved: bug-gnu-emacs@prep.ai.mit.edu Lines: 16