On Windows* operating systems, you typically do not need to set any environment variables prior to using the command line. Each of the Intel® Fortran Compiler variations has its own Intel Compiler command-line window, available from the Intel Fortran program folder. This window has the appropriate environment variables already set for the command-line environment.
Using the ifort Command from the Command Line
Use the ifort command either on a command line or in a makefile to invoke the Intel Fortran compiler. The syntax is:
For a complete listing of compiler options, see the Compiler Options reference.
You can either compile and link your projects in one step with the ifort command, or compile them with ifort and then link them as a separate step.
In most cases, you will use a single ifort command to invoke the compiler and linker.
The ifort command invokes a driver program that is the actual user interface to the compiler and linker. It accepts a list of command options and file names and directs processing for each file.
The driver program does the following:
Calls the Intel® Fortran Compiler to process Fortran files.
Passes the linker options to the linker.
Passes object files created by the compiler to the linker.
Passes libraries to the linker.
Calls the linker or librarian to create the executable or library file.
You can also use ld (Linux OS and Mac OS X) or link (Windows OS) to build libraries of object modules. These commands provide syntax instructions at the command line if you request it with the /? or /help option.
Theifort command automatically references the appropriate Intel Fortran Run-Time Libraries when it invokes the linker. Therefore, to link one or more object files created by the Intel Fortran compiler, you should use the ifort command instead of the link command.
Because the driver calls other software components, error messages may be returned by these other components. For instance, the linker may return a message if it cannot resolve a global reference. The -watch (Linux OS and Mac OS X) or /watch (Windows OS) command-line option can help clarify which component is generating the error.
Note
Windows systems support characters in Unicode* (multibyte) format; the compiler will process file names containing Unicode* characters.
Syntax Rules
The following rules apply when specifying ifort on the command line:
An option is specified by one or more letters preceded by a hyphen (-) for Linux and Mac OS* X operating systems and a slash (/) for the Windows* operating system. (You can use a hyphen (-) instead of a slash for Windows OS, but this is not the preferred method.)
You can specify more than one input_file, using a space as a delimiter. See Understanding File Extensions.
Some options take arguments in the form of filenames, strings, letters, or numbers. Except where otherwise noted, you can enter a space between the option and its argument(s) or you can combine them. For a complete listing of compiler options, see the Compiler Options reference.
You can specify more than one input_file , using a space as a delimiter. When a file is not in your path or working directory, specify the directory path before the file name. The filename extension specifies the type of file.
Note
Options on the command line apply to all files. For example, in the following command line, the -c and -nowarn options apply to both files x.f and y.f:
You cannot combine options with a single slash or hyphen, but must specify the slash or hyphen for each option specified. For example, this is correct: /1 /c
But this is not: /1c
Some compiler options are case-sensitive. For example, c and C are two different options.
Options can take arguments in the form of filenames, strings, letters, and numbers. If a string includes spaces, it must be enclosed in quotation marks.
All compiler options must precede the -Xlinker (Linux OS and Mac OS X) or /link (Windows OS) options. Options that appear following -Xlinker or /link are passed directly to the linker.
Unless you specify certain options, the command line will both compile and link the files you specify. To compile without linking, specify the -c (Linux OS and Mac OS X) or /c (Windows OS) option.
You can abbreviate some option names, entering as many characters as are needed to uniquely identify the option.
Compiler options remain in effect for the whole compilation unless overridden by a compiler directive.
On Windows OS, certain options accept one or more keyword arguments following the option name. To specify multiple keywords, you typically specify the option multiple times. However, some options allow you to use comma-separated keywords. For example:
For options that use a colon, you can use an equals sign (=) instead of the colon.
- You can redirect standard output and standard error to a file. This avoids displaying a lot of text, which will slow down execution; scrolling text in a terminal window on a workstation can cause an I/O bottleneck (increased elapsed time) and use more CPU time. See the examples in the next section.
Examples of the ifort Command
The following command compiles x.for, links, and creates an executable file. This command generates a temporary object file, which is deleted after linking:
The following command compiles x.for and generates the object file x.o (Linux OS and Mac OS X) or x.obj (Windows OS). The c option prevents linking (it does not link the object file into an executable file):
Mileage tracking form log template excel tracker sheet and. The following command links x.o or x.obj into an executable file. This command automatically links with the default Intel Fortran libraries:
The following command compiles a.for, b.for, and c.for. It creates three temporary object files, then links the object files into an executable file named a.out (on Linux OS and Mac OS X) or a.exe (Windows OS):
When you use modules and compile multiple files, compile the source files that define modules before the files that reference the modules (in USE statements).
When you use a single ifort command, the order in which files are placed on the command line is significant. For example, if the free-form source file moddef.f90 defines the modules referenced by the file projmain.f90, use the following command:
To specify a particular name for the executable file, specify the -o (Linux* OS and Mac OS* X) or /exe (Windows* OS) option:
To redirect output to a file and then display the program output (Linux* OS and Mac OS X):
To place standard output into file one.out and standard error into file two.out (Windows* OS):
Or
To place standard output and standard error into a single file both.out (Windows OS):
Or
Other Methods for using the Command Line Window to Invoke the Compiler
You can use the command-line window to invoke the Intel Fortran Compiler in a number of ways, detailed below.
Using makefiles from the Command Line
Use makefiles to specify a number of files with various paths and to save this information for multiple compilations. For more information on using makefiles, see Using Makefiles to Compile Your Application.
Using the devenv command from the Command Line (Windows only)
Use devenv to set various options for the integrated development environment (IDE) as well as build, clean, and debug projects from the command line. For more information on the devenv command, see the devenv description in the Microsoft Visual Studio* documentation.
Using a .bat file from the Command Line
Use a .bat file to consistently execute the compiler with a desired set of options. This spares you retyping the command each time you need to recompile.From: David Watson (dewatson_at_olemiss.edu)
Date:
Ifort Mac Download
Thu Jul 23 2009 - 15:03:59 CDT- Previous message:Mengjuei Hsieh: 'Re: [AMBER] errors of PMEMD installation'
- Messages sorted by:[ date ][ thread ][ subject ][ author ]
System/software configuration:
MacBook, 2 GHz Intel Core 2 Duo
Xcode 3.1.3
Intel Fortran 11.1 (058)
MPICH2-1.1.1
Ifort Mac Os
Installing developer tools:
Uninstalled previous versions of Intel Software Development Products
Installed Xcode 3.1.3
Installed Intel Fortan Compiler 11.1 (058)
Installed Intel C++ Compiler 11.1 (058)
Edited ~/.bash_profile to include
# BEGIN bash configuration for AMBER10 compilation
. /opt/intel/Compiler/11.1/058/bin/ifortvars.sh ia32
. /opt/intel/Compiler/11.1/058/bin/iccvars.sh ia32
. /Library/Frameworks/Intel_MKL.framework/Versions/Current/tools/
environment/mklvars32.sh
MPI_HOME=/opt/mpich2
export MPI_HOME
MKL_HOME=/Library/Frameworks/Intel_MKL.framework/Versions
export MKL_HOME
# END bash configuration for AMBER10 compilation
Configured MPICH2 with the following script
# BEGIN file mpich2_for_mac.sh
export CC=icc
export CFLAGS='-xHost -I/opt/intel/Compiler/11.1/058/lib'
export F77=ifort
export FFLAGS='-xHost -I/opt/intel/Compiler/11.1/058/lib'
export F90=ifort
export F90FLAGS='-xHost -I/opt/intel/Compiler/11.1/058/lib'
export CXX=icpc
export CXXFLAGS='-xHost -I/opt/intel/Compiler/11.1/058/lib'
export LDFLAGS='-L/opt/intel/Compiler/11.1/058/lib'
./configure --prefix=/opt/mpich2
# END file mpich2_for_mac.sh
Ran the mpich2 configure script, then executed 'make' and 'make
install' to install mpich2 executables and libraries in /opt/mpich2
Configured parallel installation of amber10 with
./configure_amber -openmp -mpich2 -nosanderidc ifort_macosx
Edited the config_amber.h file
added -xHost to both the FFLAGS and FOPTFLAGS
changed LOADLIB to:
LOADLIB= -L$(MKL_HOME)/lib/32 $(MKL_HOME)/lib/32/
libmkl_solver.a -lmkl_intel -lmkl_intel_thread -lmkl_core -lmkl_lapack
-openmp -lpthread
Compiled amber parallel
Proceeded to configure pmemd with
./configure linux_p4 ifort mpich2 bintraj
and made the following changes to config.h
MATH_LIBS= -L$(MKL_HOME)/lib/32 $(MKL_HOME)/lib/32/
libmkl_solver.a -lmkl_intel -lmkl_intel_thread -lmkl_core -openmp -
lpthread
MPI_LIBS = -L$(MPI_LIBDIR) -lmpich -lpthread
CPP = /usr/bin/cpp
F90 = mpif90
F90_OPT_HI = -xHost -ip -O3
LOAD = mpif90
LOADLIBS = -limf -lsvml
Compiled pmemd parallel
Nearly all of the tests, except the noesy and evb/
poh_dbonds_umb_dg_UFF_9DG* tests ran and gave acceptable results.
Go ahead, bug me again about -xHost, somebody!
The Intel Fortran Compiler User and Reference Guide says that this
option 'Can generate instructions for the highest instruction set
available on the compilation host processor.' (Fortran 11, for Mac OS X)
Is this something that shouldn't be done?
As long as I'm running it on the same host that I compiled on, this
should be fine, right?
_______________________________________________
AMBER mailing list
AMBER_at_ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
- Previous message:Mengjuei Hsieh: 'Re: [AMBER] errors of PMEMD installation'
- Messages sorted by:[ date ][ thread ][ subject ][ author ]
