Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

unable to compile wrf hydro coupled with intel llvm compilers

islas said:
It looks like configuration did not work successfully. Also, it may help log file readability if you don't run ./compile_new with -d as that is what is generating all the verbose makefile dependency graph output.
Click to expand...
ill re run it and do as you asked without -d
 
Last edited:
islas said:
It looks like configuration did not work successfully. Also, it may help log file readability if you don't run ./compile_new with -d as that is what is generating all the verbose makefile dependency graph output.
Click to expand...
I can't even replicate the error again using the same commands, so ill assume it's fixed with 4.7.0 and i'm just doing something wrong on my side. I'll come back to this once the new release comes out. Somewhere I am making a command error
 
William.Hatheway said:
I can't even replicate the error again using the same commands, so ill assume it's fixed with 4.7.0 and i'm just doing something wrong on my side. I'll come back to this once the new release comes out. Somewhere I am making a command error
Click to expand...
one thing that is confusing me is that the hydro users guide says to delete the hydro folder from the WRF git clone and replace it with the one compiled for hydro coupled. But that seems counter productive and is causing me confusion.

Either way I'll have to wait till 4.7.0 to test or if you want to message me directly @islas we can discuss it there
 
The hydro repo will not have these changes so will not work yet. I imagine that if/when the fix gets pulled in this will be flowed back to the hydro repo.
 
Yes. The hydro/ folder is also designed to be able to build without replacing it with the hydro repo's own, so it should be standalone.
 
Okay, the log file got to where about I expected it. There are already fixes for the next issue in the release branch (re: my previous comments about using the merge ref, a full working setup would be my branch fixes merged on top of the release branch), but I think this is satisfactory enough to conclude that the particular issue of linking is resolved and overall this should be fixed in v4.7.0.

William.Hatheway said:
Another question for you @islas when using the configure_new command, how do we choose between sm dm or sm+dm for options for configuring?
Click to expand...
Those are the OpenMP and MPI selections, sm and dm noted with prefix [SM] and [DM] in the prompts, respectively.
 
islas said:
Okay, the log file got to where about I expected it. There are already fixes for the next issue in the release branch (re: my previous comments about using the merge ref, a full working setup would be my branch fixes merged on top of the release branch), but I think this is satisfactory enough to conclude that the particular issue of linking is resolved and overall this should be fixed in v4.7.0.


Those are the OpenMP and MPI selections, sm and dm noted with prefix [SM] and [DM] in the prompts, respectively.
Click to expand...
Great I am so thankful this issue will be resolved in 4.7.0. Thank you again for all the help @islas
 
You must log in or register to reply here.
Top