Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Checks whether the compiler supports intrinsic storage_size() and non-bind(C)
argument x in C_FUNLOC(x).  Added them since IBM XLF 15.1 fails on these two tests.

No review since F08 binding is experimental now.

This includes a configure test to check if the compiler supports F08.

No review since F08 binding is experimental now.

While testing on the Blue Waters development system, builds failed
because the code for determining the Fortran Module options was unable to
figure out the Cray compiler (naturally, this used to work).  Investigation
showed that the compiler needs a "-em" option to create separate module
files.  This change adds a test for that, if the compiler is unable to
create module files without that option.  This also cleans up several other
minor problems with this code.

1. AC_RUN_LOG is no longer an autoconf internal macro (it might have been
at some point).  We can use it directly.

2. Replace PAC_RUNLOG_IFELSE to use autoconf-native macros, plus some
minor additional work.  Get rid of PAC_COMMAND_IFELSE and
PAC_EVAL_IFELSE, which seem to be identical to PAC_RUNLOG_IFELSE.  One
option is to just point them to PAC_RUNLOG_IFELSE, but this commit
does not do that, since they seem to be unused.  Other projects that
use these macros can just point to PAC_RUNLOG_IFELSE if needed.

3. We no longer need PAS_VAR_COPY since AS_VAR_COPY is present in
newer autoconf versions.

4. PAC_VAR_PUSHFLAG and PAC_VAR_POPFLAG are duplicates of
PAC_PUSH_FLAG and PAC_POP_FLAG.  Also, unlike the PAC_VAR_ macro
variants, the flag is not updated by the PAC_PUSH/PAC_POP macros, so
the older value is retained.

5. The AM_IGNORE macro provided in confdb only works for a patched
automake, with no patch available to use.  We should either have both
or neither.

6. aclocal_atomic.m4 is now replaced by OPA.

7. The old F77 macros were kept around as backup when we moved to the
new macros (though this is really the job of the VCS).  It's been
several years since that was done.  We can safely remove the f77old.m4
file.  It is still in git if we ever need to go back.

8. Other general cleanup.

No reviewer.

No reviewer.

BG/Q, where we do a cross-compile.

Reviewed by buntinas.

 - add a default for PAC_SET_HEADER_LIB_PATH
 - refactor it to be a bit more readable and flexible
 - several corrections to the original code which used CFLAGS and
   CPPFLAGS incorrectly.

Reviewed by buntinas.

Also error out at configure time if no module outdir flag can be
determined.

Partial fix for tt#1639.

No reviewer.

[svn-r10027] bugfix for PAC_FC_AVAIL_INTEGER_MODELS during cross-compilation so it passes correct info to PAC_FC_INTEGER_MODEL_MAP.

[svn-r10026] Replaced passing of cross-variable in PAC_FC_*MODEL*() by cross-value to be consistent with how other Fortran macros pass cross-value.

[svn-r10021] initial update of F90 datatype tests to remove the use of PAC_RUN_LOG (in preparation for cross-compile support).

Use automake+libtool instead of simplemake+createshlib.  Parallel make
now works for real, and shared library creation should be more robust on
more platforms.  "make dist" now works, modulo building the documentation,
although for boring reasons we can't actually use it for the final
distribution tarball generation.

This is a massive change and without a doubt has some bugs in it.  We'll
work through them as we find them.

No reviewer.

[svn-r8184] added m4sh-based PAC_VAR_PUSHVAL and PAC_VAR_POPVAL which provide the features needed by PAC_COMPILE_IFELSE_LOG and PAC_LINK_IFELSE_LOG.  The PAC_*_IFESLE_LOG macros simplifes PAC_*_CHECK_COMPILER_OPTION.

[svn-r7978] added requirement of AC_HEADER_STDC for tests that need it, and remove unnecessary include of standard headers.

[svn-r7918] fixed bug introduced in r7902 that leave out setting FFLAGS/FCFLAGS with cray-pointer flags if available.  Define a CRAYPTR_FFLAGS/FCFLAGS so user of the macros can choose to update FFLAGS/FCFLAGS with CRAYPTR_*FLAGS if necessary (instead update FFLAGS/FCFLAGS silently by the macros)

[svn-r7901] bugfix for PAC_PROG_FC_HAS_POINTER: clean up after AC_LANG_CONFTEST and restore FCFLAGS...

[svn-r7831] patched PAC_PROG_F*_HAS_POINTER to check for extra cray-pointer flag so allocmenf* tests can be carried if compiler support is there.  This resolves req#1079.

[svn-r7168] Reprioritize the Fortran compiler search order in PAC_PROG_F* as most Fortran users prefer non-GNU compilers if they are available.  Also relax the compiler flags being pushed/popped around AC_PROG_{compiler}.

use more recent compilers when available instead of relying on older
compilers by default: gfortran vs. g77 is one motivating example
(autoconf prefers g77 for Fortran 77). Also remove MPD specific
macros, allowing it to use confdb directly, so MPD can take advantage
of this change as well.

Reviewed by goodell.

[svn-r6940] Replaced enable_fc=default setting by enable_fc=yes and set enable_fc=no if any Fortran90 test fails.  Guarded all AC_PROG_[CC|F77|FC|CXX] so none of the *FLAGS would be set -g -O2.  Eliminated duplicated PAC_PROG_FC/PAC_PROG_FC_WORKS caused by inconsistent use of enable_fc=default.  Moved AC_PROG_[CC|F77|FC|CXX] right before the corresponding language tests to improve readability of the code.

[svn-r6852] Initial deposit that removes the AC_LANG=[Fortran 90] and replaces it by AC_LANG=[Fortran] which is officially supported by autoconf.  The replaced PAC macros in aclocal_fc.m4 is also rewritten by replacing all use of AC_TRY_* by AC_*_IFELSE style as recommented by autoconf.  The change also removes some old autoconf macros date back to at least 2.13 as in aclocal_cross.m4.  The change that users see is to use FC/FCFLAGS instead of F90/F90FLAGS which will no longer be supported.  This also includes some misc fixes that allow mpif90 to access mpi.mod during build process....

internal svn links, as supported by svn 1.5.