Skip to content
Snippets Groups Projects
Commit db7d9e56 authored by Sergey Kosukhin's avatar Sergey Kosukhin Committed by Moritz Hanke
Browse files

Major refactoring for the building system.

* Custom M4 macro are replaced with those to be used in the new ICON building
  system.
* Removed cfortran.h: the mangling scheme for Fortran symbols is detected at
  the configure-time.
* The precious variables for setting flags resuired to enable external
  packages (e.g. MTIME_C_INCLUDE, MTIME_C_LIB, etc.) are renamed to *_CFLAGS
  and *_CLIBS to better reflect their purpose. If those variables are set as
  command-line arguments of the configure script, the script checks only the
  given values literally, i.e. the script does not try to append and check any
  additional linking or compilation flags.
* The definition of functions declared in yac_lapack_interface.h is moved
  to a separate file yac_lapack_interface.c. And the choice of the interface
  is made with a single preprocessor macro YAC_LAPACK_INTERFACE_ID.
* The default suffix for include files for libxml2 is
  <XML2_ROOT>/include/libxml2 instead of <XML2_ROOT>/include.
* The configure script argument '--without-mpi-pack-external' is renamed to
  '--disable-mpi-pack-external' to reflect that it belongs to the section
  'Optional Features' and not to 'Optional Packages'. If the usage of
  MPI_Pack_external is disabled, the corresponding configure-time tests are
  skipped.
* The configure script argument '--without-regard-for-quality' is renamed to
  '--enable-mpi-checks' (defaults to 'yes'). Previously, the argument allowed
  for ignoring the failures of the configure-time tests of MPI_Pack_external.
  Now the argument allows for skipping the tests at all when specifying a
  valid interactive MPI_LAUNCH command is not possible.
* MPI_LAUNCH does not have to be a full path to an MPI launcher executable
  anymore: the value of the variable is interpreted as a command.
* AR, ARFLAGS, and RANLIB are precious variable now and appear in the help
  message of the configure script.
* The configure script does not try to detect MPI libraries, it only checks
  whether they are available (see comments in configure.ac).
parent f9d2e3b7
No related branches found
No related tags found
No related merge requests found
Showing
with 551 additions and 456 deletions
......@@ -20,22 +20,10 @@ Makefile.in
/examples/*.nc
/examples/*.sh
!/examples/toy_slurm_batch.sh
/examples/*.txt
/examples/*.xml
/examples/*.xsd
/input/*.csv
/input/*.txt
/input/*.xml
!/input/OASIS3_MCT-comp1-grid1.xml
!/input/OASIS3_MCT-comp2-grid2.xml
!/input/OASIS3_MCT-comp3-grid3.xml
!/input/OASIS3_MCT-comp3-grid4.xml
!/input/OASIS3_MCT-comp3-grid5.xml
!/input/OASIS3_MCT-comp3.xml
!/input/OASIS3_MCT-comp4.xml
!/input/cf-standard-name-table.xml
!/input/component.xml
/input/coupling.xsd
/examples/mesh_compA_convex.txt
/examples/mesh_compA_exact.txt
/src/config.h
/src/pkgconfig/yac.pc
/src/stamp-h1
......
m4_include([m4/ac_lang_program_fortran.m4])
m4_include([m4/acx_lang_fortran_check_include.m4])
m4_include([m4/acx_lang_c_check_include.m4])
......@@ -7,7 +7,7 @@
#ifndef F2C_INCLUDE
#define F2C_INCLUDE
typedef long int integer;
typedef int integer;
typedef unsigned long int uinteger;
typedef char *address;
typedef short int shortint;
......
......@@ -5,9 +5,9 @@ CLEANFILES = sysdep1.h
EXTRA_DIST = F2CLIBS/libf2c/sysdep1.h0
sysdep1.h: F2CLIBS/libf2c/sysdep1.h0
$(AM_V_GEN)cp $^ $@
$(AM_V_GEN)cp $< $@
AM_CPPFLAGS = -I$(top_srcdir)/clapack/INCLUDE
AM_CPPFLAGS = -I$(srcdir)/INCLUDE
libyac_clapack_a_SOURCES = \
BLAS/SRC/dcopy.c \
......
Your MPI library has a serious defect in its implementation
of external32 data packing. This is the only serialization guaranteed to be
portable across different MPI communicators. You can switch to the regular data
packing routines with the configure argument "--disable-mpi-pack-external".
Alternatively, you can disable this test with the configure argument
"--disable-mpi-checks" but this might result into a non-working YAC build.
test_1.txt
\ No newline at end of file
test_1.txt
\ No newline at end of file
test_1.txt
\ No newline at end of file
test_1.txt
\ No newline at end of file
Your MPI installation has a serious defect in its implementation of
external32 packing of data. This is the only serialization guaranteed
to be portable across different MPI communicators. You can elect to
use the regular data packing routines instead, for which such
portability is not guaranteed, but often works in practice with the
configure argument --without-mpi-pack-external. Alternatively you can
ignore the result of this test with the --without-regard-for-quality
option but this will probably result in a non-working YAC build,
i.e. multiple tests will fail.
test_mpi_pack_external_1.txt
\ No newline at end of file
test_mpi_pack_external_1.txt
\ No newline at end of file
test_mpi_pack_external_1.txt
\ No newline at end of file
test_mpi_pack_external_1.txt
\ No newline at end of file
This diff is collapsed.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment