* targets.c (target_vector): Take out oasys (unless that is

[deliverable/binutils-gdb.git] / README.configure

diff --git a/README.configure b/README.configure
index 253884cde84218eee206792bd37843d718810a40..c77813d5db483c0f7c81595dbcdb9e6a6174a7b5 100755 (executable)
--- a/README.configure
+++ b/README.configure
@@ -3,7 +3,7 @@
                        K. Richard Pixley
                        Cygnus Support
 
-                Last Mod 19 Jul 1991 by gnu@cygnus.com
+                Last Mod Tue Oct 1 21:20:21 PDT 1991, by rich@cygnus.com
 
 INTRO
 -----
@@ -108,20 +108,20 @@ Configuration Time Options:
     structure, the intermediate pieces used in the build process must
     be kept separate.
 
-       ./configure sun4 +forcesubdirs +notation=postfix
-       ./configure sun3 +forcesubdirs +notation=infix
+       ./configure sun4 +subdirs +notation=postfix
+       ./configure sun3 +subdirs +notation=infix
 
     will create subdirectories for the intermediate pieces of the sun4
     and sun3 configurations.  This is necessary as previous systems
     were only capable of one configuration at a time.  A second
     configuration overwrote the first.  We've chosen to retain this
-    behaviour so the "+forcesubdirs" configuration option is necessary
+    behaviour so the "+subdirs" configuration option is necessary
     to get the new behaviour.  The order of the arguments doesn't
     matter.  There should be exactly one argument without a leading
     '+' sign and that argument will be assumed to be the host name.
 
     From here on the examples will assume that you want to build the
-    tools "in place" and won't show the "+forcesubdirs" option, but
+    tools "in place" and won't show the "+subdirs" option, but
     remember that it is available.
 
     In order to actually install the program, the configuration system
@@ -212,7 +212,7 @@ BUILDING DEVELOPMENT ENVIRONMENTS
     In this example, like before, we create two configurations.  The
     first is intended to be built in a sun4 environment, in
     subdirectories, to be installed in /local.  The second is intended
-    to be build in a sun3 environment, in subdirectories, to be
+    to be built in a sun3 environment, in subdirectories, to be
     installed in /local.
 
     Unlike the previous example, the first configuration will produce
@@ -523,12 +523,12 @@ directory.
   hostname and target is targetname.  If a previous configuration
   existed, it will be overwritten.
 
-* "./configure +forcesubdirs hostname +target=targetname" creates a
-  subdirectories Host-hostname and Host-hostname/Target-targetname and
-  configures Host-hostname/Target-targetname.  For now, makes should
-  be done from Host-hostname/Target-targetname.  "./configure +f name"
-  works as expected.  That is, it creates Host-name and
-  Host-name/Target-name and configures the latter.
+* "./configure +subdirs hostname +target=targetname" creates a
+  subdirectories H-hostname and H-hostname/T-targetname and
+  configures H-hostname/T-targetname.  For now, makes should
+  be done from H-hostname/T-targetname.  "./configure +sub name"
+  works as expected.  That is, it creates H-name and
+  H-name/T-name and configures the latter.
 
 
 Hacking configurations: