[PATCH, libgfortran] Remove AM_MAKEFLAGS.

[Steve Ellcey]

> Ok.
> If it turns out that this does break ia64 again, I think we need a better 
> explanation of why.
> 
> Paul

The problem I had on ia64 was that when AM_MAKEFLAGS was not set then
CC_FOR_TARGET was undefined during the libgfortran build.  Attached is
the tail end of a makelog from before I made the change.  It looks like
CFLAGS_FOR_TARGET was not being set either.

Part of my problem may have been an old GNU make (3.76.1), I'll take out
my change and see if I can build with a newer make.

Steve Ellcey

-------

gmake[2]: Entering directory `/CLO/Products/OPENSOURCE/cvs/obj_ia_gcc/ia64-hp-hpux11.00/libgfortran'
/bin/sh ./libtool --mode=compile (CC_FOR_TARGET) -DHAVE_CONFIG_H -I. -I/CLO/Products/OPENSOURCE/cvs/gcc/libgfortran -I.  -I/CLO/Products/OPENSOURCE/cvs/gcc/libgfortran/io -O2 -g -std=gnu99 (CFLAGS_FOR_TARGET) -c -o environ.lo `test -f 'runtime/environ.c' || echo '/CLO/Products/OPENSOURCE/cvs/gcc/libgfortran/'`runtime/environ.c
/bin/sh: Syntax error at line 1 : `(' is not expected.
gmake[2]: *** [environ.lo] Error 2
gmake[2]: Leaving directory `/CLO/Products/OPENSOURCE/cvs/obj_ia_gcc/ia64-hp-hpux11.00/libgfortran'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/CLO/Products/OPENSOURCE/cvs/obj_ia_gcc/ia64-hp-hpux11.00/libgfortran'