jowr / librefprop.so

Create a shared library from the Fortran sources provided by Refprop from NIST. This project provides an alternative to the refprop.dll that comes with the software. Please use the official instructions if possible

Home Page:https://github.com/usnistgov/REFPROP-cmake

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[No rule to make target 'fortran/COMMONS.f',needed by 'src/PASS_FTN_ALT.f'. Stop]

tonkiplis opened this issue · comments

Hello,

I tried to compile the Fortran files included with Refprop 7.1 on a 10.6.8 Mac OS X system. For the purpose I followed the instructions provided on :

https://github.com/jowr/librefprop.so

and I used GCC4.2.1 and gfortran 4.6.2.

however, during the sudo make install I run into the following problem :

make: *** No rule to make target fortran/COMMONS.f', needed bysrc/PASS_FTN_ALT.f'. Stop.

it seems that the COMMONS.f is missing from my fortran directory. Did anybody encounter the same problem? Where can I find this COMMONS.f file?

With Kind Regards,

Tonkiplis

Hi. This is correct. The REFPROP code changed quite a bit over the years and the file you are referring to was introduced in REFPROP v9.1. If you provide us with a list of your filenames, we might be able to help you. However, this wrapper was built for v9.0 and v9.1 and I am not sure hiow much work it will be to include your version (v7.1) as well.

I agree; furthermore, 9.1 compared to 7.1 will have a large number of known REFPROP calculation issues repaired and include more EOS methods and improved fluid file data. For the small cost of REFPROP 9.1 its well worth it.

On Sep 29, 2014, at 9:19 AM, Jorrit Wronski notifications@github.com wrote:

Hi. This is correct. The REFPROP code changed quite a bit over the years and the file you are referring to was introduced in REFPROP v9.1. If you provide us with a list of your filenames, we might be able to help you. However, this wrapper was built for v9.0 and v9.1 and I am not sure hiow much work it will be to include your version (v7.1) as well.


Reply to this email directly or view it on GitHub.

Hello

Thanks for the quick reply! I will purchase the upgrade and keep you informed about my progresses!