Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28446 Discussions

i am executing bash script on intel parallel studio XE 2017 update 1 linux

Jobin_V_
Beginner
417 Views

Starting NMTRAN

 WARNINGS AND ERRORS (IF ANY) FOR PROBLEM    1

 (WARNING  2) NM-TRAN INFERS THAT THE DATA ARE POPULATION.
Building NONMEM Executable
FSUBS.f90(2): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [SIZES]
      USE SIZES, ONLY: DPSIZE
----------^
FSUBS.f90(3): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [NMPRD4]
      USE NMPRD4,ONLY: VRBL
----------^
FSUBS.f90(6): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      REAL(KIND=DPSIZE), DIMENSION (:),POINTER ::COM
----------------^
FSUBS.f90(7): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      REAL(KIND=DPSIZE), POINTER ::LVS,INT,SLP,AC,LOGIT,A,P,Y,A000035
----------------^
FSUBS.f90(8): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      REAL(KIND=DPSIZE), POINTER ::A000039,A000052,A000080,A000079
----------------^
FSUBS.f90(9): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      REAL(KIND=DPSIZE), POINTER ::A000051,A000074,A000109,A000112
----------------^
FSUBS.f90(10): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      REAL(KIND=DPSIZE), POINTER ::A000111,A000110,A000113
----------------^
FSUBS.f90(2): error #6580: Name in only-list does not exist.   [DPSIZE]
      USE SIZES, ONLY: DPSIZE
-----------------------^
FSUBS.f90(3): error #6580: Name in only-list does not exist.   [VRBL]
      USE NMPRD4,ONLY: VRBL
-----------------------^
FSUBS.f90(13): error #6406: Conflicting attributes or multiple declaration of name.   [VRBL]
      COM=>VRBL
-----------^
FSUBS.f90(13): error #6796: The variable must have the TARGET attribute or be a subobject of an object with the TARGET attribute, or it must have the POINTER attribute.   [VRBL]
      COM=>VRBL
-----------^
FSUBS.f90(24): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [NMPRD4P]
      USE NMPRD4P
----------^
FSUBS.f90(25): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [SIZES]
      USE SIZES,     ONLY: DPSIZE,ISIZE
----------^
FSUBS.f90(26): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [PRDIMS]
      USE PRDIMS,    ONLY: GPRD,HPRD,GERD,HERD,GPKD
----------^
FSUBS.f90(27): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [NMPRD_REAL]
      USE NMPRD_REAL,ONLY: ETA,EPS
----------^
FSUBS.f90(31): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [NMBAYES_REAL]
      USE NMBAYES_REAL, ONLY: LDF
----------^
FSUBS.f90(28): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [NMPRD_INT]
      USE NMPRD_INT, ONLY: MSEC=>ISECDER,MFIRST=>IFRSTDER,IFIRSTEM
----------^
FSUBS.f90(32): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      IMPLICIT REAL(KIND=DPSIZE) (A-Z)
-------------------------^
FSUBS.f90(33): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      REAL(KIND=DPSIZE) :: DATREC
----------------^
FSUBS.f90(35): error #6683: A kind type parameter must be a compile-time constant.   [ISIZE]
      INTEGER(KIND=ISIZE) :: ICALL,NEWIND,INDXS
-------------------^
FSUBS.f90(36): error #6683: A kind type parameter must be a compile-time constant.   [DPSIZE]
      REAL(KIND=DPSIZE) :: G(GPRD,*),H(HPRD,*)
----------------^
FSUBS.f90(38): error #6683: A kind type parameter must be a compile-time constant.   [ISIZE]
      INTEGER(KIND=ISIZE) :: FIRSTEM
-------------------^
FSUBS.f90(39): error #6406: Conflicting attributes or multiple declaration of name.   [IFIRSTEM]
      FIRSTEM=IFIRSTEM
--------------^
FSUBS.f90(60): error #6410: This name has not been declared as an array or a function.   [ETA]
      INT=THETA(001)+ETA(001)
---------------------^
FSUBS.f90(115): error #6498: The use-name for this local-name is not defined.   [MSEC]
      IF (MSEC == 1) THEN
----------^
FSUBS.f90(25): error #6580: Name in only-list does not exist.   [DPSIZE]
      USE SIZES,     ONLY: DPSIZE,ISIZE
---------------------------^
FSUBS.f90(25): error #6580: Name in only-list does not exist.   [ISIZE]
      USE SIZES,     ONLY: DPSIZE,ISIZE
----------------------------------^
FSUBS.f90(36): error #6279: A specification expression object must be a dummy argument, a COMMON block object, or an object accessible through host or use association.   [GPRD]
      REAL(KIND=DPSIZE) :: G(GPRD,*),H(HPRD,*)
-----------------------------^
FSUBS.f90(26): error #6580: Name in only-list does not exist.   [GPRD]
      USE PRDIMS,    ONLY: GPRD,HPRD,GERD,HERD,GPKD
---------------------------^
FSUBS.f90(36): error #6279: A specification expression object must be a dummy argument, a COMMON block object, or an object accessible through host or use association.   [HPRD]
      REAL(KIND=DPSIZE) :: G(GPRD,*),H(HPRD,*)
---------------------------------------^
FSUBS.f90(213): catastrophic error: Too many errors, exiting
compilation aborted for FSUBS.f90 (code 1)
No nonmem execution.

 

[root@NIBC2319 ~]# ifort -v
ifort version 17.0.1

 

gcc version 6.3.1 20161221 (Red Hat 6.3.1-1)

 

let me know if you need any other details.

0 Kudos
3 Replies
jimdempseyatthecove
Honored Contributor III
417 Views

>>FSUBS.f90(2): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [SIZES]
>>     USE SIZES, ONLY: DPSIZE
>>----------^

Is self explanatory.

SIZES.mod is apparently a module of your's or 3rd party. It is either missing or it's path is not in your INCLUDE path.

If SIZES.f90 is one of your sources, then assure that NMTRAN.f90 is dependent on SIZES.mod (and that the output of the build of SIZES.mod is placed into the expected folder).

Jim Dempsey

0 Kudos
Jobin_V_
Beginner
417 Views

it working now...thanks

 

i did nothing i just re run the script from the beganing.

 

0 Kudos
jimdempseyatthecove
Honored Contributor III
417 Views

>>i did nothing i just re run the script from the beganing

This is generally indicative that your make file is not specifying the dependencies correctly.

I suspect that you may be compiling the .f90 sources that produce the modules (.mod) together with the .f90 sources that USE the modules. To correct this, split the compiler command(s) in the make file such that the USE-ers are dependent upon the modules (.mod).

Jim Dempsey

0 Kudos
Reply