Commit a7208036 authored by Glenn Morris's avatar Glenn Morris
Browse files

Do not unconditionally define HAVE_XRMSETDATABASE on some systems

* src/s/gnu-linux.h, src/s/hpux10-20.h:
Do not unconditionally define HAVE_XRMSETDATABASE.

Maybe there was a time when this made sense, but in the current tree
it is totally illogical.  This is only used in xterm.c.  If it is set
we call XrmSetDatabase, if not we do something else.  Configure tests
for XrmSetDatabase and sets HAVE_XRMSETDATABASE accordingly.  The only
possibility that is not totally nonsensical is that the system does in
fact have XrmSetDatabase but configure failed to find it (I don't see
how this could happen though...); in which case we should fix the
configure test rather than force the results.  But this is not what
the (vague) comments say was happending.

The gnu-linux piece dates from 1995, the hpux one from 2000.!topic/gnu.emacs.bug/H24wEM8Vp9A
From: (Rainer Malzbender)
Subject: Compiling emacs 20.4 on HP-UX 10.20 with gcc
Date: 2000/02/01
Newsgroups: gnu.emacs.bug
parent 5a979817
2012-07-12 Glenn Morris <>
* s/gnu-linux.h, s/hpux10-20.h:
Do not unconditionally define HAVE_XRMSETDATABASE.
2012-07-12 Eli Zaretskii <>
* xdisp.c (insert_left_trunc_glyphs): Fix incorrect size in
......@@ -32,14 +32,6 @@ along with GNU Emacs. If not, see <>. */
your system and must be used only through an encapsulation
(Which you should place, by convention, in sysdep.c). */
/* This is to work around mysterious gcc failures in some system versions.
It is unlikely that Emacs changes will work around this problem;
therefore, this should remain permanently. */
#ifdef __ia64__
do { \
......@@ -39,12 +39,6 @@ along with GNU Emacs. If not, see <>. */
#undef srandom
#undef random
/* Rainer Malzbender <> says defining
HAVE_XRMSETDATABASE allows Emacs to compile on HP-UX 10.20 using GCC. */
/* Conservative garbage collection has not been tested, so for now
play it safe and stick with the old-fashioned way of marking. */
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment