[FLASH-USERS] Compiling on ORNL-Jaguarpf XK6

Nitesh Attal nattal at uncc.edu
Mon May 21 10:29:43 EDT 2012


/  Hi,
//
//  I am having trouble compiling FLASH3.3 or FLASH4-beta on ORNL's Jaguarpf (Cray XK6). I
//  have attempted to edit the older ORNL makefiles, and ./setup process
//  found in the sites directory, but still am not having any luck.
//
  I also tried using the Makefile.h(Attached) given to me by Anthony(http://www.flash.uchicago.edu/pipermail/flash-users/2011-November/000997.html) for///ORNL's Jaguarpf//
  /Cray XT5.

//  Does anyone know where I can find a working makefile, and the correct
//  ./setup process?
//
//  Thanks,
//
//  Nitesh///


# FLASH makefile definitions for Cray XT4 System, Jaguar at ORNL

#

# The XT4 makes use of modules. 

# Load the following modules before compiling (names as of 5th Nov 08).

#

# HDF5: module load hdf5/1.6.7_par

# PNETCDF: module load p-netcdf/1.0.2

# TAU: module load tau/2.17.2

#     use -tau=${TAUROOT}/lib/Makefile.tau-pgi-callpath-mpi-pdt at setup time.



#----------------------------------------------------------------------------

# Set the HDF5 library paths -- these need to be updated for your system

#----------------------------------------------------------------------------



MPI_PATH   =

PAPI_PATH  =

PAPI_FLAGS =

NCMPI_PATH =





#----------------------------------------------------------------------------

# Compiler and linker commands

#

#  We use the f90 compiler as the linker, so some C libraries may explicitly

#  need to be added into the link line.

#----------------------------------------------------------------------------





FCOMP   =  ftn

CCOMP   =  cc

CPPCOMP =  CC

LINK    =  ftn





#-----------------------------------------------------------------------------

# Compilation flags

#

#  Three sets of compilation/linking flags are defined: one for optimized code

#  code ("-opt"), one for debugging ("-debug"), and one for testing ("-test").

#  Passing these flags to the setup script will cause the value associated with

#  the corresponding keys (i.e. those ending in "_OPT", "_DEBUG", or "_TEST") to

#  be incorporated into the final Makefile. For example, passing "-opt" to the

#  setup script will cause the flags following "FFLAGS_OPT" to be assigned to

#  "FFLAGS" in the final Makefile. If none of these flags are passed, the default

#  behavior will match that of the "-opt" flag.

#  In general, "-opt" is meant to optimize compilation and linking. "-debug"

#  should enable runtime bounds checking, debugger symbols, and other compiler-

#  specific debugging options. "-test" is useful for testing different

#  combinations of compiler flags particular to your individual system.

#----------------------------------------------------------------------------



FFLAGS_OPT   = -c -r8 -i4 -fastsse -Minfo -Mneginfo

FFLAGS_DEBUG = -c -r8 -i4 -g -Ktrap=divz -Mchkfpstk -Mchkptr -Mchkstk -Mdclchk -Mbounds

FFLAGS_TEST  = -c -r8 -i4 -Mprof=lines



CFLAGS_OPT   = -c -fastsse

CFLAGS_DEBUG = -c -g

CFLAGS_TEST  = -c



#No path required because we are using compiler wrapper scripts.

FFLAGS_MPI   =

CFLAGS_MPI   =



# if we are using HDF5, we need to specify the path to the include files

CFLAGS_HDF5  = ${HDF5_CLIB}

CFLAGS_NCMPI = ${PNETCDF_LIB}



FFLAGS_PAPI  =



#----------------------------------------------------------------------------

# Linker flags

#

#  There is a seperate version of the linker flags for each of the _OPT,

#  _DEBUG, and _TEST cases.

#----------------------------------------------------------------------------



LFLAGS_OPT   = -o  #if using IPA need it on link line too -Mipa=fast,inline

LFLAGS_DEBUG = -g -o

LFLAGS_TEST  = -Mprof=lines -o



#----------------------------------------------------------------------------

# Library specific linking

#

#  If a FLASH module has a 'LIBRARY xxx' line in its Config file, we need to

#  create a macro in this Makefile.h for LIB_xxx, which will be added to the

#  link line when FLASH is built.  This allows us to switch between different

#  (incompatible) libraries.  We also create a _OPT, _DEBUG, and _TEST

#  library macro to add any performance-minded libraries (like fast math),

#  depending on how FLASH was setup.

#----------------------------------------------------------------------------



LIB_HDF5    = ${HDF5_FLIB}

              

LIB_MPI     =

LIB_PAPI    =

LIB_PNG     =



LIB_OPT     =

LIB_DEBUG   =

LIB_TEST    =



LIB_NCMPI   = ${PNETCDF_LIB}

LIB_MPE     =

#----------------------------------------------------------------------------

# Additional machine-dependent object files

#

#  Add any machine specific files here -- they will be compiled and linked

#  when FLASH is built.

#----------------------------------------------------------------------------



MACHOBJ =



#----------------------------------------------------------------------------

# Additional commands

#----------------------------------------------------------------------------



MV    = mv -f

AR    = ar -r

RM    = rm -f

CD    = cd

RL    = ranlib

ECHO  = echo

AWK   = awk

CAT   = cat



---------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://flash.rochester.edu/pipermail/flash-users/attachments/20120521/5280643e/attachment.htm>


More information about the flash-users mailing list