[comp.emacs] Gnu Emacs X interface under Sys V

pinkas@cadev4.intel.com (Israel Pinkas ~) (11/10/87)

I recently brought up Gnu Emacs on a Sys V.3 box running X10R4.  I wanted
to have the emacs X support, so I defined the proper constants in the
appriopriate files and so on.  The compiler complained when compiling
xterm.c and xfns.c.  The complaints were about undefined constants and
macros that are defined on our BSD systems.

My question is:  Has anybody managed to bring Emacs up with the X support
on a Sys V.3 machine, and if so what did you have to do?

-Israel

----------------------------------------------------------------------
Disclaimer: The above are my personal opinions, and in no way represent
the opinions of Intel Corporation.  In no way should the above be taken
to be a statement of Intel.

UUCP:	{amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!cadev4!pinkas
ARPA:	pinkas%cadev4.intel.com@relay.cs.net
CSNET:	pinkas%cadev4.intel.com

---------
"You can do more with a kind word and a gun than with just a kind word"

			-Al Capone

rlk@think.COM (Robert Krawitz) (11/10/87)

In article <1275@mipos3.intel.com> pinkas@cadev4.intel.com writes:
]I recently brought up Gnu Emacs on a Sys V.3 box running X10R4.  I wanted
]to have the emacs X support, so I defined the proper constants in the
]appriopriate files and so on.  The compiler complained when compiling
]xterm.c and xfns.c.  The complaints were about undefined constants and
]macros that are defined on our BSD systems.

The things that are undefined are probably related to SIGIO, which
emacs uses internally to make C-g "interrupts" work under X.  Sigio is
a berkeley mechanism for asynchronous, interrupt-driven I/O which I'm
told has no equivalent in SysV.

I have been warned about this, and I'm aware that it causes problems
for SysV users, but I have no good idea about how to fix it.  You can
take out all the references to SIGIO and it might work, but C-g
certainly won't and you'll probably have redisplay problems.  The
places where emacs actually sends itself a SIGIO you might be able to
simulate by calling the SIGIO handler directly, but I haven't ever
tried this.

cca >>>>>>>>>>  |
harvard >>>>>>  |
bloom-beacon >  |think!rlk	Robert Krawitz <rlk@think.com>
rutgers >>>>>>  |
ihnp4 >>>>>>>>  .