help configure project for HPC - non-standard ways to run the executable
Hi, I'm new to this list. I develop a Fortran 2008 coarrays project targeting HPC systems. I'd like to simplify my build process with autotools. The immediate problem is that the executable is run in different ways on different platforms. For example, OpenCoarrays compiler is "caf", but the executable is run with "cafrun -np .. ./a.out". This is similar to "mpif90" and "mpirun" for MPI programs. On Cray I compile with "ftn" and run with "aprun" (it's also cross-compiled, but I'm not there yet). So I get errors like: configure:2850: caf -o conftestconftest.f >&5 configure:2854: $? = 0 configure:2861: ./conftest [mpie...@20474701626e.anet.bris.ac.uk] match_arg (utils/args/args.c:159): unrecognized argument pmi_ args [mpie...@20474701626e.anet.bris.ac.uk] HYDU_parse_array (utils/args/args.c:174): argument matching r eturned error [mpie...@20474701626e.anet.bris.ac.uk] parse_args (ui/mpich/utils.c:1596): error parsing input array [mpie...@20474701626e.anet.bris.ac.uk] HYD_uii_mpx_get_parameters (ui/mpich/utils.c:1648): unable to parse user arguments [mpie...@20474701626e.anet.bris.ac.uk] main (ui/mpich/mpiexec.c:153): error parsing parameters because the invocation should have been "cafrun -np .. ./conftest" for this compiler. Is there a standard way of implementing this in configure.ac? I looked at ax_prog_fc_mpi: https://www.gnu.org/software/autoconf-archive/ax_prog_fc_mpi.html which looks similar but not exactly what I need. Thanks Anton ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
Re: [Autoconf] help configure project for HPC - non-standard ways to run the executable
> From mpsuz...@hiroshima-u.ac.jp Thu Sep 21 01:39:51 2017 > > What kind of the automation you want to realize by autotool? At present I have a collection of Makefiles, one for each platform (HPC system, compiler, libraries, etc.). This works ok, but sometimes the users are not sure which libraries are available or which they should use, i.e. they are not sure which Makefile to use. I was wondering if I can automate this choice with autotools. You mention cross-compiling. However, my examples with mpif90 and mpirun, or caf and cafrun, are native, not cross-compiling. The executables are run on the same platform, it's just the invocation of the executable is not simply ./a.out, but "mpirun -np ./a.out", or "cafrun -np ./a.out". Anyway, it sounds that autotools will give me more headache than help. Thanks! Anton ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
