Any additional information related to this implementation, that came to light after the release of this product, is described below.
First it is necessary to compile the NAG module files for use with your version of the compiler. This process is described in the Users' Note for flw3224dcl, but is also given below for convenience.
In a DOS command window, go to the folder containing your installed copy of the NAG Library, for example c:\Program Files\NAG\FL23\flw3224dcl. Then, the following commands will compile the modules:
mkdir nag_interface_blocks_gfortran copy nag_interface_blocks\*.f90 nag_interface_blocks_gfortran cd nag_interface_blocks_gfortran gfortran -c nag_precisions.f90 gfortran -c *_ib.f90 gfortran -c *blas*.f90 gfortran -c nag_long_names.f90 gfortran -c nag_library.f90Note that the order of compilation is important because some modules depend on others. Once all the modules have successfully compiled you should have a complete set of .mod files. The associated .o object files may be deleted as they are not required.
Once the module files are created, you can compile and link a program to the NAG library as shown below. Note that we use one of the NAG example programs for demonstration, and assume that the NAG library has been installed in the default location.
gfortran -I"C:\Program Files\NAG\FL24\flw3224dcl\nag_interface_blocks_gfortran" e04ucfe.f90 "C:\Program Files\NAG\FL24\flw3224dcl\lib\FLW3224DC_nag.lib" -o e04ucfe.exeSo long as your PATH environment variable contains the folder where the NAG DLL FLW3224DC_nag.dll is installed, you should now be able to run the program:
e04ucfe.exe < e04ucfe.dLimitations
It is not possible to link to the static libraries that are distributed with FLW3224DC, e.g. nag_nag_MD.lib, because the name mangling used by gfortran means the symbol names in your program do not match those in the static NAG libraries. Correct symbol names are only exported by the DLLs.