-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MET 11.1.0 unable to install on MacOS using Homebrew #2775
Comments
line 134/135 of the netcdf-cxx install log |
Hi @HathewayWill. Could you please try changing the following line in compile_MET_all.sh from:
to
and see if you get a successful compilation? Please let us know how it goes. Thanks! |
sadly that didn't work, here are the log files again. |
Found a solution to netcdfcxx but I don't know why. Needed configure_lib_args="-lnetcdf -lm -lhdf5_hl -lhdf5 -lz" |
but now we have a different error: met.configure.log very confused @jprestop |
Hi @HathewayWill. I see in the met.make_test.log file:
Let's check on your NetCDF installations. Can you please tell me if all of the following files exist in your /Users/workhorse/WRF/MET-11.1.0/external_libs/include and /Users/workhorse/WRF/MET-11.1.0/external_libs/lib directories? Files for NetCDF4 C: Files for NetCDF4 C++: |
for netcdf-c++ I had to add -lm and -lnetcdf |
@HathewayWill Ah yes, very confusing indeed. I think @georgemccabe figured out the problem. The compile_MET_all.sh script was running "make test" using MAKE_ARGS. Since some tests rely on the output of other tests to succeed, running "make test" in parallel won't work and explains the confusing information in the log file where it says it is running wavelet_stat, but then the log information refers to grid_stat. I have modified the compile_MET_all.sh script and have added "-lnetcdf -lm" to configure_lib_args for the compilation of NetCDF-CXX. Please download the new script and try again. |
So does make test need to have the make args removed for each one if running in parallel processing? I'm running a WRF run right now but give me tonight and I'll test it later. Sounds like that was the error which will make everyone happy that it's fixed using dtc-mosit and WRF-mosit |
I don't think I understand your question. I'm not sure what you mean by "each one". To help clarify, we changed:
to
Maybe you mean - does ${MAKE_ARGS} need to be removed in calls to the external libraries' "make test" commands? If so, the answer, unfortunately, is I don't know if the external libraries "make test" commands rely on the output of other tests to succeed. All I can say is that I haven't experienced this problem previously in installations on various machines, so I think until we encounter a problem it is likely ok to leave as-is. |
That was what I was getting at. You answered my question about the removal. Sorry for the confusion |
Testing it now. Was reading the new compile_MET script and I noticed that the make install for met doesn't have MAKE ARGS. Can met not be installed in parallel?
|
tested it and it got worse. Before it would fail at test now it fails at met.make Here is the relevant log files. |
Removing ${MAKE_ARGS} from "make install" and "make test" for MET. Removing "met" prefix from met.configure.log because we really need config.log for any detail. It is confusing to have met.configure.log when that does not contain useful information.
@jprestop @georgemccabe different error now. |
I'm wondering if these files are corrupted:
Could you please send them to us following the directions here? |
@jprestop I'm having issues with ubuntu and the ftp protocol. |
You could also try to attached the files here, @HathewayWill. |
not sure if you can get this otherwise email me directly |
Hi @HathewayWill. Well, the NetCDF files do not seem to be corrupted. I copied them over and ran "ncdump" on them, and that worked fine. I also copied them to our project machine and ran the command that is causing you problems:
but I got a successful run. I did not have the problem you are experiencing:
Let's have you try running the same command outside of "make test". In the directory
Please give that a try and post the output here. Please let me know if you have any questions. |
I'm going to rebuild the mac and test it again, i can't even repeat the error on my own machine, now it is stopping before the previous error. Do you have a mac machine available there? |
Hi @HathewayWill. We have two developers who have successfully installed MET-11.1 on their Macs. One was using 13.6.2 (Ventura) and the other was using 12.6.2 (Monterey). Both compiled using the GNU compilers. |
Morning @jprestop Okay that's good to know. Let me rebuild my mac and double check on my side. I wonder if it's the shell script. Are they using homebrew GNU compilers or something else? |
@HathewayWill. They both used GNU compilers that were installed via MacPorts. |
Might be the solution I'm using homebrew. Can you ask them which gnu version of macports they are using |
I would think that Homebrew and MacPorts would be similar, but it could be an issue. One of the developers was using MacPorts 12.3.0 and also used the compile_MET_all.sh script successfully. |
So for grins I tried to compile MET v11.0.0 using the same structure for installation as I did with V11.1.0 V11.0.0 didn't install so I am going to check my structure. |
Got it to work on MacOS Sonoma but not 100% on MacOS Ventura. Ventura the MET Tests have errors but metplus still runs sucessfully The fixes worked that you implemented it on Sonoma but I have attached the logs for Ventura. |
And now Sonoma doesn't work. This is very confusing to me. |
@jprestop @georgemccabe @JohnHalleyGotway With you're permission i'm going to close this issue and open two different ones for the different mac operating systems. I think there is two different issues going on for each OS and I want to keep them seperate. I will reference this issue though in the new ones if that is okay with you? |
Hi @HathewayWill. This situation is certainly very strange, particularly considering our developers have has successful compilations on various Mac OSs. This could be something in your environment, although it's not clear yet. Even though MET's configure ran successfully for you, I do see the following error:
The other developers did not receive that error. I have their config.log files and would like to step through to see the differences, but I haven't have had a chance to look into the above error or to compare the log files yet. |
I will retest and see what I can find and attach log files here. |
Replace italics below with details for this issue.
Describe the Problem
MET 11.1.0 fails to build NETCDF-CXX
Expected Behavior
MET would compile like 11.0.0
Environment
Describe your runtime environment:
*1. Machine: Virtual Machine
*2. OS: MacOS 13
*3. Software version number(s): 13.4 beta
To Reproduce
See attached zip file with logs and compile.sh script
MET_FAIL_MACOS.zip
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Milestone and Projects
Define Related Issue(s)
Consider the impact to the other METplus components.
Bugfix Checklist
See the METplus Workflow for details.
Branch name:
bugfix_<Issue Number>_main_<Version>_<Description>
Pull request:
bugfix <Issue Number> main_<Version> <Description>
Select: Reviewer(s) and Development issue
Select: Milestone as the next bugfix version
Select: Coordinated METplus-X.Y Support project for support of the current coordinated release
Branch name:
bugfix_<Issue Number>_develop_<Description>
Pull request:
bugfix <Issue Number> develop <Description>
Select: Reviewer(s) and Development issue
Select: Milestone as the next official version
Select: MET-X.Y.Z Development project for development toward the next official release
The text was updated successfully, but these errors were encountered: