emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r100340: * src/[ms]/template.h: Comme


From: Glenn Morris
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r100340: * src/[ms]/template.h: Comments.
Date: Mon, 17 May 2010 19:59:15 -0700
User-agent: Bazaar (2.0.3)

------------------------------------------------------------
revno: 100340
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Mon 2010-05-17 19:59:15 -0700
message:
  * src/[ms]/template.h: Comments.
modified:
  src/m/template.h
  src/s/template.h
=== modified file 'src/m/template.h'
--- a/src/m/template.h  2010-05-12 02:37:59 +0000
+++ b/src/m/template.h  2010-05-18 02:59:15 +0000
@@ -69,11 +69,14 @@
    reasonable place to select for it is in the machine description file.  */
 #define NO_SOCK_SIGIO
 
-/* After adding support for a new system, modify the large case
-   statement in the `configure' script to recognize reasonable
+/* After adding support for a new machine, modify the large case
+   statement in configure.in to recognize reasonable
    configuration names, and add a description of the system to
    `etc/MACHINES'.
 
+   Check for any tests of $machine in configure.in, and add an entry
+   for the new machine if needed.
+
    If you've just fixed a problem in an existing configuration file,
    you should also check `etc/MACHINES' to make sure its descriptions
    of known problems in that configuration should be updated.  */

=== modified file 'src/s/template.h'
--- a/src/s/template.h  2010-05-12 06:53:03 +0000
+++ b/src/s/template.h  2010-05-18 02:59:15 +0000
@@ -133,10 +133,13 @@
 /* ============================================================ */
 
 /* After adding support for a new system, modify the large case
-   statement in the `configure' script to recognize reasonable
+   statement in configure.in to recognize reasonable
    configuration names, and add a description of the system to
    `etc/MACHINES'.
 
+   Check for any tests of $opsys in configure.in, and add an entry
+   for the new system if needed.
+
    If you've just fixed a problem in an existing configuration file,
    you should also check `etc/MACHINES' to make sure its descriptions
    of known problems in that configuration should be updated.  */


reply via email to

[Prev in Thread] Current Thread [Next in Thread]