Another minor bug introduced during mkcheck.in split (and not caught during the partial remerge)?

[Loren James Rittle]

If you look at version 1.41 of mkcheck.in (just before the split), you
can see that SH_FLAG and ST_FLAG were used.  They became S[TH]_FLAGS
in the new tests_flags.in file and were copied back that way.  Fully
bootstrapped on alpha-unknown-freebsd4.2 (see next port report) with
the testsuite report checked by hand to ensure that both -static and
dynamic builds were now occurring.

Speaking of bootstrap: I know these are bogus, tiny changes; but they
need to be, at the very least, rebuilt (fully bootstrapped if not
contained inside a library, such as this minor change) and checked for
correctness too!

Regards,
Loren

2000-12-01  Loren J. Rittle  <ljrittle@acm.org>

        * mkcheck.in: Correct typo.

Index: mkcheck.in
===================================================================
RCS file: /cvs/gcc/egcs/libstdc++-v3/mkcheck.in,v
retrieving revision 1.43
diff -c -r1.43 mkcheck.in
*** mkcheck.in	2000/11/29 03:54:39	1.43
--- mkcheck.in	2000/12/01 10:16:15
***************
*** 57,67 ****
  IFS=$saved_ifs
  
  # specific libtool flag(s) to force the use of shared libraries, if any
! SH_FLAGS=
  
  # specific libtool flag(s) to force the use of static libraries, if any
! ST_FLAGS="-static"
! #ST_FLAGS="-all-static"
  
  # Set up the testing directory, which should be in a directory called
  # "testsuite" in the root level of the build directory.
--- 57,67 ----
  IFS=$saved_ifs
  
  # specific libtool flag(s) to force the use of shared libraries, if any
! SH_FLAG=
  
  # specific libtool flag(s) to force the use of static libraries, if any
! ST_FLAG="-static"
! #ST_FLAG="-all-static"
  
  # Set up the testing directory, which should be in a directory called
  # "testsuite" in the root level of the build directory.