Re: NAT_FILE set incorrectly in gdb/Makefile

[Eli Zaretskii <eliz@gnu.org>]

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: gdb-patches@sourceware.org
> Date: Sun, 19 Apr 2009 23:35:05 +0200
> 
> Does this help?  Most likey config.status was run twice with different
> values of CONFIG_FILES.

I believe you are right: it's run once for Makefile, and then again
for .gdbinit:

  for ac_config_target in $ac_config_targets
  do
    case "$ac_config_target" in
    # Handling of arguments.
    "Makefile" ) CONFIG_FILES="$CONFIG_FILES Makefile" ;;
    ".gdbinit" ) CONFIG_FILES="$CONFIG_FILES .gdbinit:gdbinit.in" ;;
    "gnulib/Makefile" ) CONFIG_FILES="$CONFIG_FILES gnulib/Makefile" ;;
    "$ac_config_links_1" ) CONFIG_LINKS="$CONFIG_LINKS $ac_config_links_1" ;;
    "depdir" ) CONFIG_COMMANDS="$CONFIG_COMMANDS depdir" ;;
    "depfiles" ) CONFIG_COMMANDS="$CONFIG_COMMANDS depfiles" ;;
    "default" ) CONFIG_COMMANDS="$CONFIG_COMMANDS default" ;;
    "config.h" ) CONFIG_HEADERS="$CONFIG_HEADERS config.h:config.in" ;;
    *) { { echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5
  echo "$as_me: error: invalid argument: $ac_config_target" >&2;}
     { (exit 1); exit 1; }; };;
    esac
  done

Yes, your patch solves the problem.  (I don't have Autoconf 2.59, so I
patched configure manually, rather than patching configure.ac and
regenerating configure.)

Thanks.