
error message during compiling eos4
Dear Stefan
iam trying to compile eos4 following the same steps mentioned in the manual and read me file
using comaq compiler fortran 6.5
the file are ma28.f t2cg2.f meshm.f t2f.f eos4.f t2solv.f
no double names in the subroutines
but i had this problem or message error:
--------------------Configuration: tough2 - Win32 Debug--------------------
Compiling Fortran...
Compaq Visual Fortran Optimizing Compiler Version 6.5
Copyright 2000 Compaq Computer Corp. All rights reserved.
C:\Documents and Settings\source code\TOUGH2 source code\T2SOLV.F
df: info: Some interprocedural optimizations may be disabled when compiling into separate object files
C:\Documents and Settings\source code\TOUGH2 source code\T2f.f
C:\Documents and Settings\source code\TOUGH2 source code\T2CG2.F
C:\Documents and Settings\source code\TOUGH2 source code\T2CG2.F(1775) : Warning: Variable IFLAG is used before its value has been defined
PRINT 6001,TD,IFLAG
-----------------------^
C:\Documents and Settings\source code\TOUGH2 source code\MESHM.F
C:\Documents and Settings\source code\TOUGH2 source code\MA28.F
Compiling Fortran...
Compaq Visual Fortran Optimizing Compiler Version 6.5
Copyright 2000 Compaq Computer Corp. All rights reserved.
C:\Documents and Settings\source code\TOUGH2 source code\EOS4.F
Linking...
EOS4.OBJ : error LNK2001: unresolved external symbol _PCAP@16
EOS4.OBJ : error LNK2001: unresolved external symbol _RELP@28
Debug/tough2.exe : fatal error LNK1120: 2 unresolved externals
Error executing link.exe.
tough2.exe - 3 error(s), 1 warning(s)
when i chek i found that eos4.f is version 1.1
and other files are version 2 is that the reason?
i do not know the real cause of this problem could you please recommend me something
all the best,
madi
-
Madi,
Just check in file t2f.f whether teh subroutines pcap and relp are there - it appears they have been renamed (e.g., because the code was previously compiled with another EOS module that has its own (three-phase) versions). You can ignore the warning message.
I just read your second post. You simply have to look in your project set-up to find where the executable can be found. It can often be found in folder DEBUG.
Stefan