Hi Brad:
While trying to set up a clean Experimental dashboard, I have noticed
a minor spelling issue (furhter ==> further in
a comment in cmake_common.cmake).
I also noticed a somewhat more serious issue concerning the consistency
of build flags. I attempted to use consistent compile flags as
follows:
set(ENV{CXXFLAGS} "-O3 -DNDEBUG")
set(ENV{CFLAGS} "-O3 -DNDEBUG")
set(CTEST_BUILD_CONFIGURATION None)
This "first" method apparently did generate consistent build flags,
but the complex, complexOneConfig, Preprocess, and Qt4Deploy tests
failed (see the first Experimental "raven" results on 2017-10-26 for
commit fc3668).
A similar test with None replaced above by Release (call this the
"second" method) was headed to a
similar failure (I noticed Preprocess had failed and quit the test before
it encountered the other 3 failures and before a dashboard was submitted).
So I fell back to using a "third" method which was
unset(ENV{CXXFLAGS})
unset(ENV{CFLAGS})
# Just in case any of the Fortran tests pay attention to FFLAGS which
# I often set.
unset(ENV{FFLAGS})
set(CTEST_BUILD_CONFIGURATION Release)
That gave a completely clean result (see the second Experimental
"raven" results on 2017-10-26 for commit fc3668). I also followed up
with a Nightly raven result (generated by crontab). That also gave a
perfectly clean result (see the first Nightly "raven" results on
2017-10-26 for commit da363e). So it looks like I am basically in
business (except for the PLplot build part of the test that you
plan to work on as time permits).
However, one of the deficiencies of this third method is the
bootstrap script only pays attention to CXXFLAGS and CFLAGS when
setting compile flags for building the preliminary version of CMake so
that build is unoptimized in this case which will significantly add to
the time taken to configure the build of the full version of CMake
(although that time is likely negligible compared to the time required
to pass all the 500 tests).
If you know of a simple way to fix this inconsistency between the
compile flags used to build the preliminary and final versions of
CMake, please let me know.
I thought the first method I tried above would do exactly that (since
the adopted CXXFLAGS and CFLAGS should give you exactly the same as
"Release" on Linux, but that method also causes those four test
failures for unknown reasons. So if you feel the first method should
be supported, then the solution of this issue would be to debug
whatever is wrong on the CMake end for those 4 test failures.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
