Closed gassmoeller closed 5 years ago
Hey Rene,
are you using the current version in aspect, or the most resent version of the world builder? The 'n' warning should be gone in the new versions.
My gcc testers use gcc 6.5.0, and I see no warnings or errors there (https://travis-ci.org/GeodynamicWorldBuilder/WorldBuilder/jobs/484079093). I will go through the compiler flags to see if I can reproduce the codepoint error.
I will also test the world builder flag, and fix it if necessary.
I use the latest version that is in aspect. With the latest version of the Worldbuilder itself the warning about n
is gone, but the codepoint
error is still there.
I have now also tested it in 4.9 and 6.5.0 (through travis) with the flags -Wmaybe-uninitialized and -Werror=maybe-uninitialized and I do not see the warning. The problem itself is easy to fix, but the weird thing is that just 2 lines later the value is set anyway. I will try to install gcc 6.2 on travis to see whether I can reproduce the error, before I fix it.
I have not been able to reproduce the problem (installing gcc 6.2 is a hassle), so I just initialized the value. Could you update to world builder to see whether the problem is gone?
I think pull request #2778 should fix the other issue.
Yes that fixed it. The newest world build compiles without issues. I suppose the problems are really just caught in the tester docker container (with deal.II 8.5). Thanks for the quick response!
Great!
The current version of the WorldBuilder produces warnings with gcc 6.2.0 as follows:
This prevents me from compiling in the tester docker container, because I can also not disable the world builder (-D ASPECT_WITH_WORLD_BUILDER=OFF has no effect, if the world build is there, it tries to compile it).