Re: How to generate test reports?

[Matthias Klose <Matthias.Klose@cs.tu-berlin.de>]

Alexandre Oliva writes:
> I've attached a new version of this script, that is expected to comply 
> with these requirements.

gawk is not available on all systems.

Fri May 22 00:33:52 1998  Matthias Klose  <doko@cs.tu-berlin.de>

	* test_summary: find good awk (copied from warn_summary).

*** gcc/test_summary~	Thu May 21 00:44:58 1998
--- gcc/test_summary	Fri May 22 00:32:26 1998
***************
*** 31,36 ****
--- 31,48 ----
  # -t: prevents logs from being renamed
  # -m: specify the e-mail address to send notes to.  An appropriate default should be selected from the log files.
  # -f: force reports to be mailed; if omitted, only reports that differ from the sent.* version are sent
+ 
+ # Find a good awk.
+ if test -z "$AWK" ; then
+   for AWK in gawk nawk awk ; do
+     if type $AWK 2>&1 | grep 'not found' > /dev/null 2>&1 ; then
+       :
+     else
+       break
+     fi
+   done
+ fi
+ 
  : ${filesuffix=}; export fileprefix
  : ${move=true}; export move
  : ${forcemail=false}; export forcemail
***************
*** 63,69 ****
  done &&
  $anyfile &&
  if $forcemail || $anychange; then :; else mailto=nobody; fi &&
! gawk '
  BEGIN {
    lang="";
    print "cat <<EOF |";
--- 75,81 ----
  done &&
  $anyfile &&
  if $forcemail || $anychange; then :; else mailto=nobody; fi &&
! $AWK '
  BEGIN {
    lang="";
    print "cat <<EOF |";