Index: dejagnu.texi
===================================================================
RCS file: /cvsroot/dejagnu/dejagnu/doc/dejagnu.texi,v
retrieving revision 1.2
diff -c -p -r1.2 dejagnu.texi
*** dejagnu.texi	2001/02/18 05:12:07	1.2
--- dejagnu.texi	2001/05/30 17:56:47
*************** o\input texinfo               @c        
*** 4,10 ****
  @c
  @c This file documents the GNU Testing Framework ``DejaGnu''
  @c
! @c Copyright (C) 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software Foundation, Inc.
  @c
  @c This text may be freely distributed under the terms of the GNU
  @c General Public License.
--- 4,10 ----
  @c
  @c This file documents the GNU Testing Framework ``DejaGnu''
  @c
! @c Copyright (C) 92, 93, 94, 95, 96, 97, 98, 99, 2000, 2001 Free Software Foundation, Inc.
  @c
  @c This text may be freely distributed under the terms of the GNU
  @c General Public License.
*************** and test a cross compiler on a machine o
*** 1290,1296 ****
  hosted on.
  
  Here we have the config settings for our California office. Note that
! all config values are site dependant. Here we have two sets of values
  that we use for testing m68k-aout cross compilers. As both of these
  target boards has a different debugging protocol, we test on both of
  them in sequence.
--- 1290,1296 ----
  hosted on.
  
  Here we have the config settings for our California office. Note that
! all config values are site dependent. Here we have two sets of values
  that we use for testing m68k-aout cross compilers. As both of these
  target boards has a different debugging protocol, we test on both of
  them in sequence.
*************** variable in the top section, then just p
*** 1422,1432 ****
  second section. Usually the values defined in this config file are
  related to the configuration of the test run. This is the ideal place to
  set the variables @code{host_triplet}, @code{build_triplet},
! @code{target_triplet}. All other variables are tool dependant. ie for
  testing a compiler, the value for @var{CC} might be set to a freshly
  built binary, as opposed to one in the user's path.
  
! @node Personal Config File, , Local Config File, Customizing
  @subsection Personal Config File
  @cindex personal config @file{site.exp}
  @cindex @file{site.exp} for each person
--- 1422,1432 ----
  second section. Usually the values defined in this config file are
  related to the configuration of the test run. This is the ideal place to
  set the variables @code{host_triplet}, @code{build_triplet},
! @code{target_triplet}. All other variables are tool dependent, i.e., for
  testing a compiler, the value for @var{CC} might be set to a freshly
  built binary, as opposed to one in the user's path.
  
! @node Personal Config File, Local Config File, Customizing
  @subsection Personal Config File
  @cindex personal config @file{site.exp}
  @cindex @file{site.exp} for each person
*************** set compiler_conditional_xfail_data @{@ 
*** 1938,1944 ****
    What this does is it matches only for these two targets if "-Wall -v" or 
  "-O3" is set, but neither "-O1" or "-Map" is set.
  
!   For a set to match, the options specified are searched for independantly of
  each other, so a "-Wall -v" matches either "-Wall -v" or "-v -Wall". A space
  seperates the options in the string. Glob-style regular expressions are also
  permitted.
--- 1938,1944 ----
    What this does is it matches only for these two targets if "-Wall -v" or 
  "-O3" is set, but neither "-O1" or "-Map" is set.
  
!   For a set to match, the options specified are searched for independently of
  each other, so a "-Wall -v" matches either "-Wall -v" or "-v -Wall". A space
  seperates the options in the string. Glob-style regular expressions are also
  permitted.
Index: ref.sgml
===================================================================
RCS file: /cvsroot/dejagnu/dejagnu/doc/ref.sgml,v
retrieving revision 1.5
diff -c -p -r1.5 ref.sgml
*** ref.sgml	2001/05/06 16:22:20	1.5
--- ref.sgml	2001/05/30 17:56:48
***************
*** 854,860 ****
  
  	  <para>What this does is it matches only for these two targets if
  	  "-Wall -v" or  "-O3" is set, but neither "-O1" or "-Map" is set. For
! 	  a set to match, the options specified are searched for independantly
  	  of each other, so a "-Wall -v" matches either "-Wall -v" or "-v
  	  -Wall". A space seperates the options in the string. Glob-style
  	  regular expressions are also permitted.</para>
--- 854,860 ----
  
  	  <para>What this does is it matches only for these two targets if
  	  "-Wall -v" or  "-O3" is set, but neither "-O1" or "-Map" is set. For
! 	  a set to match, the options specified are searched for independently
  	  of each other, so a "-Wall -v" matches either "-Wall -v" or "-v
  	  -Wall". A space seperates the options in the string. Glob-style
  	  regular expressions are also permitted.</para>
***************
*** 3133,3139 ****
  	</sect3>
  
      </sect2>
!     <sect2 id=platformprocs xreflabel="platform dependant procedures">
        <title>Platform Dependant Procedures</title>
  
        <para>Each combination of target and tool requires some
--- 3133,3139 ----
  	</sect3>
  
      </sect2>
!     <sect2 id=platformprocs xreflabel="platform dependent procedures">
        <title>Platform Dependant Procedures</title>
  
        <para>Each combination of target and tool requires some
Index: user.sgml
===================================================================
RCS file: /cvsroot/dejagnu/dejagnu/doc/user.sgml,v
retrieving revision 1.5
diff -c -p -r1.5 user.sgml
*** user.sgml	2001/05/06 16:22:20	1.5
--- user.sgml	2001/05/30 17:56:50
***************
*** 859,865 ****
        the test run. This is the ideal place to set the variables
        <symbol>host_triplet</symbol>, <symbol>build_triplet</symbol>,
        <symbol>target_triplet</symbol>. All other variables are tool
!       dependant. ie for testing a compiler, the value for
        <symbol>CC</symbol> might be set to a freshly built binary, as
        opposed to one in the user's path.</para>
  
--- 859,865 ----
        the test run. This is the ideal place to set the variables
        <symbol>host_triplet</symbol>, <symbol>build_triplet</symbol>,
        <symbol>target_triplet</symbol>. All other variables are tool
!       dependent, i.e., for testing a compiler, the value for
        <symbol>CC</symbol> might be set to a freshly built binary, as
        opposed to one in the user's path.</para>
  
***************
*** 910,916 ****
        one it's to be hosted on.</para>
  
        <para>Here we have the config settings for our California
!       office. Note that all config values are site dependant. Here we
        have two sets of values that we use for testing m68k-aout cross
        compilers. As both of these target boards has a different
        debugging protocol, we test on both of them in sequence.</para>
--- 910,916 ----
        one it's to be hosted on.</para>
  
        <para>Here we have the config settings for our California
!       office. Note that all config values are site dependent. Here we
        have two sets of values that we use for testing m68k-aout cross
        compilers. As both of these target boards has a different
        debugging protocol, we test on both of them in sequence.</para>
Index: overview/builtins.html
===================================================================
RCS file: /cvsroot/dejagnu/dejagnu/doc/overview/builtins.html,v
retrieving revision 1.2
diff -c -p -r1.2 builtins.html
*** overview/builtins.html	2001/02/22 05:47:35	1.2
--- overview/builtins.html	2001/05/30 17:56:51
*************** CLASS="PROGRAMLISTING"
*** 2015,2021 ****
  ><P
  >What this does is it matches only for these two targets if
  	  "-Wall -v" or  "-O3" is set, but neither "-O1" or "-Map" is set. For
! 	  a set to match, the options specified are searched for independantly
  	  of each other, so a "-Wall -v" matches either "-Wall -v" or "-v
  	  -Wall". A space seperates the options in the string. Glob-style
  	  regular expressions are also permitted.</P
--- 2015,2021 ----
  ><P
  >What this does is it matches only for these two targets if
  	  "-Wall -v" or  "-O3" is set, but neither "-O1" or "-Map" is set. For
! 	  a set to match, the options specified are searched for independently
  	  of each other, so a "-Wall -v" matches either "-Wall -v" or "-v
  	  -Wall". A space seperates the options in the string. Glob-style
  	  regular expressions are also permitted.</P
Index: overview/customizing.html
===================================================================
RCS file: /cvsroot/dejagnu/dejagnu/doc/overview/customizing.html,v
retrieving revision 1.2
diff -c -p -r1.2 customizing.html
*** overview/customizing.html	2001/02/22 05:47:35	1.2
--- overview/customizing.html	2001/05/30 17:56:51
*************** CLASS="SYMBOL"
*** 355,361 ****
  CLASS="SYMBOL"
  >target_triplet</SPAN
  >. All other variables are tool
!       dependant. ie for testing a compiler, the value for
        <SPAN
  CLASS="SYMBOL"
  >CC</SPAN
--- 355,361 ----
  CLASS="SYMBOL"
  >target_triplet</SPAN
  >. All other variables are tool
!       dependent, i.e., for testing a compiler, the value for
        <SPAN
  CLASS="SYMBOL"
  >CC</SPAN
Index: overview/global.html
===================================================================
RCS file: /cvsroot/dejagnu/dejagnu/doc/overview/global.html,v
retrieving revision 1.2
diff -c -p -r1.2 global.html
*** overview/global.html	2001/02/22 05:47:35	1.2
--- overview/global.html	2001/05/30 17:56:52
*************** CLASS="EMPHASIS"
*** 81,87 ****
        one it's to be hosted on.</P
  ><P
  >Here we have the config settings for our California
!       office. Note that all config values are site dependant. Here we
        have two sets of values that we use for testing m68k-aout cross
        compilers. As both of these target boards has a different
        debugging protocol, we test on both of them in sequence.</P
--- 81,87 ----
        one it's to be hosted on.</P
  ><P
  >Here we have the config settings for our California
!       office. Note that all config values are site dependent. Here we
        have two sets of values that we use for testing m68k-aout cross
        compilers. As both of these target boards has a different
        debugging protocol, we test on both of them in sequence.</P