d847e10d96
Some configuration scripts probe and just set HAVE_FOO without any values, whereas others set it explicitly to 1. If these two are mixed, for instance that the same package is used by two of our prerequisites, but in different manner, then we get compatibility warnings when we try to run the configuration script, even though there is no real conflict. dune-fem, dune-alugrid and dune-localfunctions have this problem (around release 2018.04). This patch special-code the test so if the old value was previously either just defined or explicitly set to the value 1, a warning will not be issued if then suddenly the other variant is used.
opm-common
Contains common components used throughout all of OPM, in particular CMake modules for the build system.