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
broken configuration when using ccmake on Ubuntu #720
Comments
Maciek, do you think that is caused by our build system? Or could it be a ccmake problem in the first place? |
It's hard to tell. I think reporting it is important, since we wasted inordinate amount of time looking for misconfigured compilation flags, linking scripts, etc., while the workaround (using cmake instead of ccmake) is trivial. It wouldn't be good for some inexperienced user to have to go through all the effort to diagnose this issue. It may be a ccmake problem, it may just as well be an indication that something is still not quite right with HPX configuration macros. Is there a reason for the contents of cmake cache to be so different in both cases? |
Since I do not understand enough of ccmake and how it invokes cmake underneath, I'm not able to tell where the differences come from (I didn't even know that you could pass variable values to ccmake via its command line). I agree that documenting this problem is important, however I'm not sure if we can do anything about it except for reporting the issue to the cmake/ccmake maintainers. Experience shows that any change to a cmake variable might take proper effect only after the cache is regenerated from scratch. I'll go ahead and add something to that effect to our build system docs. |
One of the major problems with the way HPX uses CMake currently is the overly abuse of cache variables. Most variables flagged as cacheable really don't belong into the cache. I am not sure if this is related to the issue at hand. |
Thomas I believe what you describe is unrelated. The problem described here is just the result of a bug in
while |
Hartmut -- that's correct. In both cases the configuration was done in completely empty build directories. After dealing with cmake for a while, this and wiping out the prefix directory before the installation becomes your second nature. |
I believe that Thomas Heller's statement is absolutely correct. |
This should be fixed by ecdb034. Please reopen if the problem still persists. |
On Ubuntu 12.04 using ccmake instead of cmake apparently generates broken configuration that prevents correct compilation of
examples.gtcx
. The command line options passed to cmake/ccmake are identical and listed below:-DCMAKE_INSTALL_PREFIX=/home/maciek/packages/hpx-gtc -DHWLOC_ROOT=/opt/hwloc/1.6.1 -DBOOST_ROOT=/opt/boost/1.53.0 -DHDF5_ROOT=/opt/hdf5/1.8.10/ -DHDF5_CPP_ROOT=/opt/hdf5/1.8.10/ -DHDF5_FORTRAN_ROOT=/opt/hdf5/1.8.10/ ..
. The resultant cmake cache files in respective build directories differ as follows:This problem has not been encountered so far on other distributions. Cmake versions tried were 2.8.7 (system installation) and 2.8.10.2 (compiled); both exhibit the same behavior. The resultant compilation error is:
The text was updated successfully, but these errors were encountered: