Last week I pulled back some cmake changes related to #3137, having to do with building a static shadow. It built fine on my dev environment, but failed in our release build env. I eventually tracked the problem to a bug in cmake-2.6, which caused the shared libcondor_utils to be created, and then later deleted, mid-build.
This particular problem has an easy workaround, namely:
add_dependencies( condor_utils condor_utils_s )
This morning I noticed that the cmake glue on the current master failed outright with cmake-2.6 Our release builds use 2.6 natively, so maintaining compatibility with 2.6 is a nontrivial issue for us. I imagine some are easy to find and fix, but the above bug turned out to be in cmake itself, and I spent three days rooting it.
Including a cmake-2.6 build as part of the regular upstream build suite seems like a good idea. And/or making it SOP for us developers to do a test build against cmake-2.6 whenever we are making modifications to the cmake glue.
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}