It seems the modified Makefile works right now. However, it generates another question/error message. What is those two lines mean?
What will be the direction to solve it? The original code just ransuccessfully under Compaq Fortran Compiler, but I encountered several problems in Intel fortran Compiler.
Is that possible the FFLAG in Makefile causes this error? Quoting - kuo-hsien-changs-macbook-pro:CNCLASS cks$./runclass 1990 89 forrtl: No such file or directory forrtl: severe (29): file not found, unit 89, file /Users/cks/CNCLASS/fort.89 I hope you are able to look at your own source code.
My guess is that you fail to use OPEN to create the file for unit 89, instead depending on the compiler run time to create a file, in a non-portable style of 35 years ago. Then you assume that a file will be created with the default naming convention of some past compiler, and you fail to use iostat to help your program to display a diagnosis. Even in that style, without help from the programmer, the user may have difficulty understanding the error when the program attempts to read from a non-existent file, the run time creates an empty file, and the read still fails. I don't believe there are compile command line flags to fix this. Quoting - I hope you are able to look at your own source code. My guess is that you fail to use OPEN to create the file for unit 89, instead depending on the compiler run time to create a file, in a non-portable style of 35 years ago.
EcoEuroMillions Shareware is commonly installed in the C: Program Files (x86) ecoeuromillions directory, but this location may differ a lot depending on the user's decision when installing the program. EcoEuroMillions Shareware's full uninstall command line is C: Program Files (x86) ecoeuromillions unins000.exe. Autochk* program not found - skipping AUTOCHECK The message shows up after the windows logo and before the logon screen. I can still run windows just fine with no problems what-so-ever.
Then you assume that a file will be created with the default naming convention of some past compiler, and you fail to use iostat to help your program to display a diagnosis. Even in that style, without help from the programmer, the user may have difficulty understanding the error when the program attempts to read from a non-existent file, the run time creates an empty file, and the read still fails. I don't believe there are compile command line flags to fix this. You already point out the difficulty I suffered to run the whole program, such as the different user compiler, the background of programmer and users, and to understand the error. I have to think about any possibilities to make it works in this computer. I look at the source code and only the main program entitled 'runclass' has the 'OPEN' setting and the unit number did not have 89 and even 100 which is thefort.100 crated after running 'runclass'.
Kuo-hsien-changs-macbook-pro:CNCLASS cks$./runclass 1990 89 forrtl: No such file or directory forrtl: severe (29): file not found, unit 89, file /Users/cks/CNCLASS/ fort.89 Is that possible that the I/O causes this problem? In previous trials, I got this error message as below. The program seems to run. Because the error message was 'forrtl: severe (174): SIGSEGV, segmentation fault occurred' so that I back to modify the Makefile. After solving this error, another error 'file notfound, unit 89' came out.
Based on youprogramming experiences, please feel free to advice more. It seems almost there, but I really need some helps. Thanks.:: 0 soil water balance error @ 1990 365 23 0 snow layer energy balance error @ 1990 365 23 30 1st soil layer energy balance error @ 1990 365 23 30 2nd soil layer energy balance error @ 1990 365 23 30 3rd soil layer energy balance error @ 1990 365 23 30 soil water balance error @ 1990 365 23 30 forrtl: severe (174): SIGSEGV, segmentation fault occurred.
![Software Software](http://www.downloadcollection.com/graphics/largeimages/weighbridge_software_free-895734.jpeg)
To expand on what Tim said, the program is attempting to read from unit 89 but has not opened a file on that unit. What happens then is that a default filename of fort.89 is constructed and Fortran tries to open that file. It was not found. To solve this, you will have to understand what the program is trying to do at this point and see where it should have opened unit 89. It's possible that the program was intended to be run with an environment variable defined to point to the input file, but that seems unlikely to me.
Quoting - To expand on what Tim said, the program is attempting to read from unit 89 but has not opened a file on that unit. What happens then is that a default filename of fort.89 is constructed and Fortran tries to open that file. It was not found. To solve this, you will have to understand what the program is trying to do at this point and see where it should have opened unit 89.
![File File](http://images2015.cnblogs.com/blog/535328/201509/535328-20150918110701414-932397555.png)
It's possible that the program was intended to be run with an environment variable defined to point to the input file, but that seems unlikely to me. Hi Steve, I was looking into the source code, but I did not find any open commend with unit 89. I also use the searching tool to go through each line contains 'unit', however the unit '89' did not exist. One of users ran this code long time ago suggested that to check the Intel Fortran Compiler setting, because the source code itself output some error files but may not explicitly open it in the main program(runclass). I'm just wondering the Intel Fortran Setting might be the problem.
The source code was designed under Compaq Fortran Compiler. How to set up a proper compiler environment for this source code? Thanks again. If Makefile contains 'FFLAGS= -fp -i64 -realsize 64 -integersize 64 -nosave', then the error message was: kuo-hsien-changs-macbook-pro:CNCLASS cks$./runclass 1990 45 starting year. 1990 forrtl: severe (174): SIGSEGV, segmentation fault occurred Image PC Routine Line Source runclass 05FA57 Unknown Unknown Unknown runclass 05ECD0 Unknown Unknown Unknown runclass 000ABC Unknown Unknown Unknown runclass 000A54 Unknown Unknown Unknown kuo-hsien-changs-macbook-pro:CNCLASS cks$ If the Makefile did not contains any flags, the the error message was: kuo-hsien-changs-macbook-pro:CNCLASS cks$./runclass 1990 41 starting year. Quoting - READ(89.) is the same as READ(unit=89.); likewise with WRITE and PRINT. We suggested that your problem stemmed from omission of an OPEN for unit 89.
Dear all, It works, if I did not use the the spinup option.(I guess.) If I use the spinup up option, it will show the error message,forrtl: severe (174): SIGSEGV, segmentation fault occurred. Kuo-hsien-changs-macbook-pro:CNCLASS cks$./runclass starting year. 2002 starting year.
2003 starting year. 2004 starting year. 2005 starting year.
2006 starting year.