one override the module and tell it what to use?
On 09/14/2018 12:30 PM, Mateusz Loskot wrote:
On Fri, 14 Sep 2018 at 20:57, Burlen Loring wrote:
why did they MPI_C_LIBRARIES and MPI_C_INCLUDE_DIRS/PATH get changed from cache
variables to not chached variables?
Possibly, that change was due
Hi Chuck,
I have a an install of mpi that has no compiler wrappers. I know the
include dir and the list of libraries to use. How do I tell the new
cmake module? Is it no longer supported to tell the module what to use
for these?
Burlen
On 09/17/2018 06:46 AM, Chuck Atkins wrote:
Hi Burlen
of the issue. Now how does one override the detection and tell it
what to use in the new module?
Burlen
On 09/14/2018 10:32 AM, Chuck Atkins wrote:
Hi Burlen,
_LIBRARIES and _INCLUDE_DIRS are non-cached output variables. The new
functionality should be documented as to how to guide the current
runs?
Burlen
--
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
post install step. How have others solved this
issue?
Thanks
Burlen
--
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 offe
I have the above error after having to upgrade CMake on my Mac. I have
read posts on SO and this list about this issue, stating that it is
caused by Boost release being newer than Cmake. However it seems that it
is also can be caused by Boost release being older than CMake since this
version
m.
https://github.com/LBL-EESA/TECA/blob/master/alg/gfdl_tc_candidates.h
It's a bit of a heavy handed solution, but I think you can solve your
problem in a similar way. I'm interested in hearing of other approaches
that have worked.
Burlen
On 06/26/2017 01:40 PM, Juan E. Sanchez wr
upgrading from cmake 3.7.1 to cmake version 3.8.2 resolved the issue.
On 06/02/2017 11:53 AM, Burlen Loring wrote:
After upgrading to latest XCode and command line tools on OSX Sierra
our project that uses CMake to mix C++ and Fortran fails to configure.
Full output below. Any ideas?
here
After upgrading to latest XCode and command line tools on OSX Sierra our
project that uses CMake to mix C++ and Fortran fails to configure. Full
output below. Any ideas?
here are version
cmake version 3.7.1
GNU Fortran (Homebrew GCC 7.1.0) 7.1.0
Apple LLVM version 8.1.0
lds. clang and intel also support these flags, although there
may be better alternatives.
What do you think?
Burlen
--
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
documentation about it.
Burlen
--
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://
After digging though a number of closed bug reports I found an open
issue in mantis that describes the problem exactly and has a number of
proposed solution. I took one of them(c39236) and this seems to do the
trick.
https://cmake.org/Bug/view.php?id=14809
On 12/23/2015 08:54 AM, Burlen
I found that there is an install of gcc in /usr/local/ and this was
causing the issue. once I removed that things went smoothly.
On 12/23/2015 09:00 AM, Burlen Loring wrote:
I tried to download and compile 3.4.1 on Apple 10.10.5. I did
./configure prefix=blah && make
here is t
ibpython2.7.dylib)
I suppose I can just over ride these manually, but shouldn't this just
work? or am I doing it wrong?
Burlen
ps.
I tried to install cmake 3.4 on my system but bootstrap has a compile error.
I observed the same with cmake 3.4.1 on a colleagues Apple system that
has system Py
because homebrew installed gcc. All the same,
shouldn't this just work? If Cmake can't work with homebrew gcc then
should it ignore it?
Burlen
--
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
on
the widget for each set of diffs?
Burlen
--
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
to find
corresponding text output which has some useful information about the
failure. it would be helpful if the images were shown inline with test
output. Is this possible?
Thanks
Burlen
http://missmarple.lbl.gov/CDash/testDetails.php?test=145428build=693
--
Powered by www.kitware.com
Please
On 11/04/2013 10:49 PM, Rolf Eike Beer wrote:
Am Montag, 4. November 2013, 16:09:04 schrieb burlen:
Can a test return a value to indicate that it could not be run?
http://cmake.org/Bug/view.php?id=8466
Thanks for pointing this out, I think that would be a very useful feature.
--
Powered
polluting the dashboard, and it's probably a good idea to keep
it like this. However, I think it's an issue that it's difficult to tell
which tests are being skipped on which systems and it would be very
useful if these tests showed up in the dashboard as not run rather than
passed.
Burlen
On 09/24/2012 09:29 AM, burlen wrote:
On 09/24/2012 07:04 AM, Bill Hoffman wrote:
On 9/23/2012 4:29 PM, Burlen Loring wrote:
hmmm, I was a bit hasty in concluding that the issue has gone away in
newer releases. on another system, I have the issue with cmake 2.8.8.
The intel compiler version
On 09/24/2012 07:04 AM, Bill Hoffman wrote:
On 9/23/2012 4:29 PM, Burlen Loring wrote:
hmmm, I was a bit hasty in concluding that the issue has gone away in
newer releases. on another system, I have the issue with cmake 2.8.8.
The intel compiler version there is 11.1. On this system if I don't
. Am I doing something wrong or is this in fact a bug?
Thanks
Burlen
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
I'm not having the issue with a newer version of intel compiler and
cmake 2.8.8. I'm concluding that this is not an issue in current releases.
Burlen
On 9/23/2012 9:08 AM, Burlen Loring wrote:
Hi,
When I'm using intel compilers cmake is missing some of the internal
compiler include paths
. There are no *INCLUDE* env vars set,
however CC,CPP,CXX,F90 etc are set correctly to point at the intel
compilers.
On 9/23/2012 10:39 AM, Burlen Loring wrote:
I'm not having the issue with a newer version of intel compiler and
cmake 2.8.8. I'm concluding that this is not an issue in current
Hi all,
I am running a dashboard on a system which I suspect has periodically
high network loads leading to the more than occasional ctest submission
timeout(ex below). Is it possible to tell ctest to retry or adjust the
timeout value?
Thanks
Burlen
Error when uploading file:
/usr/common
Great! Thanks
Burlen
On 09/17/2012 08:26 AM, David Cole wrote:
See the RETRY_DELAY and RETRY_COUNT parameters to ctest_submit:
http://www.cmake.org/cmake/help/v2.8.9/ctest.html#command:ctest_submit
On Mon, Sep 17, 2012 at 11:16 AM, burlenburlen.lor...@gmail.com wrote:
Hi all,
I am
26 matches
Mail list logo
