ctarbide

diff --git a/src/OSD/OSD_MemInfo.cxx b/src/OSD/OSD_MemInfo.cxx
index 8a9f10e09d..0406ef15b0 100644
--- a/src/OSD/OSD_MemInfo.cxx
+++ b/src/OSD/OSD_MemInfo.cxx
@@ -13,6 +13,8 @@
 // Alternatively, this file may be used under the terms of Open CASCADE
 // commercial license or contractual agreement.
 
+#define __GENERIC_LIB_C__
+

ctarbide

/* copied from snprintf.c, except for HAVE_VA_COPY and HAVE___VA_COPY
   since va_copy is not available in c89

gcc -I. -DHAVE_CONFIG_H -DTEST_SNPRINTF -Wall -Werror -std=c89 -c -o snprintf.o snprintf.c

gcc -I. -DHAVE_CONFIG_H -Wall -Werror -std=c89 -c -o snprintf.o snprintf.c

 */

#ifndef HAVE_STDARG_H

ctarbide

Emacs isn't just an editor, it’s an entire Emacs Lisp interpreter and environment. We can use Emacs Lisp not only to extend and customize our beloved editor, but also to write entire programs and applications. Nic Ferrier’s [elnode][] server is the most ambitious Emacs Lisp application of this sort, but we can start at a smaller scale and try to write our shell scripts and tools with Emacs Lisp.

However, it turns out that writing programs in Emacs Lisp is more intricate than it looks at a first glance. Emacs decades-long history as interactive application have left deep marks in Emacs and Emacs Lisp, which make independent