--- /dev/null
+/* machine description file for Silicon Graphics Iris 2500 Turbos;
+ also possibly for non-turbo Irises with system release 2.5.
+ Copyright (C) 1985, 1986 Free Software Foundation, Inc.
+
+This file is part of GNU Emacs.
+
+GNU Emacs is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+
+GNU Emacs is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with XEmacs; see the file COPYING. If not, write to
+the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+Boston, MA 02111-1307, USA. */
+
+/* Synched up with: FSF 19.31. */
+
+/* The following line tells the configuration script what sort of
+ operating system this machine is likely to run.
+ USUAL-OPSYS="note"
+NOTE-START
+Version 18 said to work; use -opsystem=irist3-5 for system version 2.5
+and -opsystem=iris3-6 for system versions 3.6 and up.
+NOTE-END */
+
+#if 0
+ Message-Id: <8705050653.AA20004@orville.arpa>
+ Subject: gnu emacs 18.41 on iris [23].5 machines
+ Date: 04 May 87 23:53:11 PDT (Mon)
+ From: raible@orville.arpa
+
+ Aside from the SIGIOT, I know of only one bug, a real strange one:
+ I wrote a utimes interface, which copies elements from timevals
+ to utimbufs. This code is known good. The problem is that in
+ emacs, the utime doesn't seem to take effect (i.e. doesn't change the
+ dates at all) unless I call report_file_error *after* the utime returns!
+
+ if (utime (name, &utb) < 0)
+ return;
+ else
+ /* XXX XXX XXX */
+ /* For some reason, if this is taken out, then the utime above breaks! */
+ /* (i.e. it doesn't set the time. This just makes no sense... */
+ /* Eric - May 4, 1987 */
+ report_file_error ("Worked just find\n", Qnil);
+
+ Without any sort of debugger that works on emacs (I know... but I don't have
+ *time* right now to start with gdb), it was quite time consuming to track
+ it down to this.
+
+ But since this code is only used for an optional 4th argument to one command
+ (copy-file), it would say that it is non-critical...
+#endif /* 0 */
+
+/* Now define a symbol for the cpu type, if your compiler
+ does not define it automatically:
+ Ones defined so far include vax, m68000, ns16000, pyramid,
+ orion, tahoe, APOLLO and many others */
+
+#ifndef m68000
+#define m68000
+#endif
+
+/* Data type of load average, as read out of kmem. */
+
+#define LOAD_AVE_TYPE long
+
+/* Convert that into an integer that is 100 for a load average of 1.0 */
+
+#define FSCALE 1.0
+#define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE)
+
+/* Define CANNOT_DUMP on machines where unexec does not work.
+ Then the function dump-emacs will not be defined
+ and temacs will do (load "loadup") automatically unless told otherwise. */
+
+/* #define CANNOT_DUMP */
+
+/* Define C_ALLOCA if this machine does not support a true alloca
+ and the one written in C should be used instead.
+ Define HAVE_ALLOCA to say that the system provides a properly
+ working alloca function and it should be used.
+ Define neither one if an assembler-language alloca
+ in the file alloca.s should be used. */
+
+/* #define C_ALLOCA */
+#define HAVE_ALLOCA
+
+/* Define NO_REMAP if memory segmentation makes it not work well
+ to change the boundary between the text section and data section
+ when Emacs is dumped. If you define this, the preloaded Lisp
+ code will not be sharable; but that's better than failing completely. */
+
+/* #define NO_REMAP */
+
+/* There is an inconsistency between the sgi assembler, linker which barfs
+ on these. */
+
+#define internal_with_output_to_temp_buffer stupid_long_name1
+#define Finsert_abbrev_table_description stupid_long_name2
projects / chise / xemacs-chise.git- / blobdiff