-
Notifications
You must be signed in to change notification settings - Fork 27
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
Suppress WARNING messages when building GCHP #322
Comments
I think this may be due to the GCHP compiler flags using -Wall (all warnings on) in the CMakeLists. |
Suppressing these warnings sounds good to me! |
Fyi, it's possible the -Wall was seen in GEOS and thus kept around. I am building GEOSgcm right now and see lots of warnings. |
This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue. |
@mathomp4, I have been playing around with trying to suppress the warning messages when building MAPL, FV3, etc in GCHP but so far have been unsuccessful. Do you have precedent for doing this in GEOSgcm? If yes, could you point me to where that is done? I wonder if there is a hook when building with ESMA_cmake/ecbuild? |
@lizziel @msulprizio @mathomp4: I wonder if the easier solution is to fix the code to remove the obsolete features (like multiple DO loops ending on a single CONTINUE). That might open a new can of worms, though, especially if some of the code is in submodules that are maintained by others. Just a thought. |
Is this with GCC or Intel? With Intel it's often fairly simple to suppress warnings. With GCC, it can be a bit harder, but often possible. |
@lizziel We've done a good job making the MAPL build be fairly warning free (to the point we can). But I'll take a look and see if I can suppress more... |
We are still using MAPL 2.26.0, so perhaps we should just be patient for MAPL 3... |
Well, MAPL 3 is a long way off. But I think MAPL 2.40 had much of the "clean up warnings" work. But 26->40 is a bit of a jump itself. Sadly, it looks like for gfortran, you can't individually suppress certain warnings like you can with intel. You suppress them all, or not. :( |
I think we should keep this feature request on the back-burner for now. The warnings are not causing problems and there will likely be fewer in the future. |
Name and Institution (Required)
Name: Melissa Sulprizio
Institution: Harvard / GCST
Confirm you have reviewed the following documentation
New GCHP feature or discussion
When building GCHP with CMake there are numerous warnings. For example:
These warnings can make users think that something is going wrong with the build, when they can be safely ignored in most cases. Ideally, these issues would be fixed, but most if not all of the warnings originate in GMAO libraries and would need to be fixed in those codes. In the meantime, we may be able to suppress the warnings by passing an argument to CMake (e.g. using
-Wno-dev
ortarget_compile_options(-w)
).The text was updated successfully, but these errors were encountered: