GCC top-level configure versus contrib/test_summary

[David Edelsohn <dje at watson dot ibm dot com>]

	contrib/test_summary prints the LAST_UPDATE date by finding the
source directory in config.status:

cat ./config.status $files |
$AWK '
BEGIN {
  lang="";
  address="gcc-testresults@gcc.gnu.org";
  version="gcc";
  print "cat <<'"'"'EOF'"'"' |";
'${prepend_logs+"  system(\"cat $prepend_logs\"); "}'
}
$1 ~ /\/configure$/ {
    srcdir = $1;
    gsub(/\/configure$/, "", srcdir);
    printf "LAST_UPDATED: ";
    system("tail -1 " srcdir "/LAST_UPDATED");
    print "";

    $1 = "configure flags:"; configflags = $0;
    gsub(/--with-gcc-version-trigger=[^ ]* /, "", configflags);
    gsub(/ --norecursion/, "", configflags)
}

The important line is

	$1 ~ /\/configure$/ {

Prior to the configure update, config.status looked like:

#!/bin/sh
# This file was generated automatically by configure.  Do not edit.
# This directory was configured as follows:
/usr/gnu/src/gcc-3.2/configure ...

Now config.status looks like:

#! /bin/sh
# Generated automatically by configure.
# Run this file to recreate the current configuration.
# This directory was configured as follows,
#
# /gcc/dje/src/configure ...

Notice that $srcdir/configure no longer is in the first column.
contrib/test_summary needs to be updated.  It may still be confused by
other items in the new config.status.

David