NOTE: The instructions to compile and execute a Fortran 90 program calling one or more IMSL routines begins at section "Putting It Together" below. You can ignore the background information that precedes that section.
/opt/lib/imsl_toolkit_1.1/CTT1.1/ INSTALL bristol bin help include notes versions bristol cnl (IMSL C Numerical Libraries Version 2.0) f90 (IMSL Fortran 90 MP Library Version 3.0) fnl (IMSL Fortran Numerical Libraries Version 3.01) version.table examples/solaris/f90/manual/ (example programs) . . examples/solaris_1/f90/manual/ (example programs) . . ctt/bin/ * cttsetup.csh solaris.csh solaris_1.csh . . * lib/lib.solaris/ blas.ll build_blas exblas.ll imslfnl.dat imslerr.bin imsls_e.bin libimsl.a libimsl.so libimsl.so.3.1 libimslcmath.a libimslcmath.so libimslcmath.so.2.1 libimslcmathsup_imsl.a libimslcmathsup_imsl.so libimslcmathsup_imsl.so.2.1 libimslcmathsup_perf.a libimslcmathsup_perf.so libimslcmathsup_perf.so.2.1 libimslcstat.a libimslcstat.so libimslcstat.so.2.1 lib/lib.solaris_1/libimsl.a blas.ll build_blas exblas.ll imslfnl.dat libimsl.a libimsl.so libimsl.so.3.1The "*" items above are those that are directly relevant to compiling and running an F90 program calling an IMSL routine.. The lib.solaris directory contains the IMSL routine library libimsl.a as well as other necessary libraries. The cctsetup.csh file needs to be sourced to define the necessary environment variables. This file, in turn, calls on the solaris.csh file. It selects solaris.csh as opposed to solaris_1.csh via computing the architecture, which is "solaris". I.e., see file cctsetup.csh which uses commands:
setenv VNI_DIR /opt/lib/imsl_toolkit_1.1 setenv CTT_DIR $VNI_DIR/CTT1.1 setenv VNI_ARCH `$CTT_DIR/ctt/bin/arch`
/opt/workshop4/SUNWspro/SC4.2/lib
alias f90imslsetup 'source /opt/lib/imsl_toolkit_1.1/CTT1.1/ctt/bin/cttsetup.csh' alias f90imsl '/opt/workshop4/SUNWspro/SC4.2/bin/f90 \!* -o \!$:r.exe $F90FLAGS $LINK_F90'
f90imslsetupfollowed by
f90imsl myprogram.f90The compilation using the f90imsl alias will produce an executable with the same name as your f90 source program and a suffix of ".exe" For example, "myprogram.exe". Note that you need only type f90imslsetup once preceding your IMSL f90 compilations and executions.
% xterm & % f90imslsetupThe first command opens a second xterm window; the second sets up the vars for IMSL work in your original window. Note the order of the commands. If you do the reverse, the environment variables will carry over to the second xterm window which is what you don't want.