Hi Eike,
So, it seems that voyager has no issue, only pioneer, which I'm just taking
as coincidence from differences in various binary sizes. However, from
looking at the error log, the link line for cmake shows:
/usr/bin/c++ -Wnon-virtual-dtor -Wcast-align -Wchar-subscripts -Wall -W
-Wshadow
Am Donnerstag, 6. November 2014, 10:37:25 schrieb Chuck Atkins:
Hi Eike,
So, it seems that voyager has no issue, only pioneer, which I'm just taking
as coincidence from differences in various binary sizes. However, from
looking at the error log, the link line for cmake shows:
Aha! I'll change it to MATCHES instead of STREQUALS and that should do it
since technically the issue is with both 32 and 64 bit architectures, it
just might not have shown up yet on both. Perhaps the build name for the
dashboard should be HPPA64 then instead HPPA32?
- Chuck
On Thu, Nov 6,
Am Donnerstag, 6. November 2014, 10:58:36 schrieben Sie:
Aha! I'll change it to MATCHES instead of STREQUALS and that should do it
since technically the issue is with both 32 and 64 bit architectures, it
just might not have shown up yet on both. Perhaps the build name for the
dashboard
I hate MATCHES ;) at least make it MATCHES ^parisc.
A reasonable compromise.
The branch has been updated, merged, squashed, and remerged to next. We'll
see what happens tonight.
- Chuck
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On 11/06/2014 11:22 AM, Chuck Atkins wrote:
The branch has been updated, merged, squashed, and remerged to next
Thanks. This hunk:
# Determine whether this is Linux
if echo ${cmake_system} | grep Linux /dev/null 21; then
cmake_system_linux=true
# find out if it is a HP PA-RISC machine
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15235
==
Reported By:Andrew Aladjev
Assigned To:
Rats! I keep forgetting about the bootstrap. I added an HP-UX block and
adjusted the logic to be a bit more consistent with the other determine
system blocks by moving the parisc determination out on it's own. How's
this?
# Determine whether this is HP-UX
if echo ${cmake_system} | grep HP-UX
On 11/06/2014 12:00 PM, Chuck Atkins wrote:
I added an HP-UX block and adjusted the logic to be a bit more
consistent with the other determine system blocks
Looks good to me, assuming the test for parisc on hpux is correct.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic
On 04/11/14 21:21, Brad King wrote:
On 11/04/2014 03:10 PM, Gregor Jasny wrote:
About the continue() outside of a block error: I added a test but I
have no idea how to enforce the desired behavior.
It's been a while since I looked at the relevant parts of the code
but here is one approach
On 11/06/2014 03:20 PM, Gregor Jasny wrote:
As you can see in the patch the if command detects the continue
invocation and aborts looping over the collected commands.
Right.
IMHO what's needed is a in loop counter that counts how deep we are in a
loop construct. It gets incremented within
Using the netcdf project
ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-4.3.2.tar.gz
I see a problem with incremental builds doing a relink of libraries. Within
my project, this leads to unnecessarily relinking of many executables every
time I run cmake.
For example:
tar zxf
Am Donnerstag, 6. November 2014, 12:44:12 schrieb Brad King:
On 11/06/2014 12:00 PM, Chuck Atkins wrote:
I added an HP-UX block and adjusted the logic to be a bit more
consistent with the other determine system blocks
Looks good to me, assuming the test for parisc on hpux is correct.
These are the earliest CDash results available for CMake:
http://open.cdash.org/index.php?project=CMakedate=2014-07-09
(they're discarded after 120 days...)
On Thu, Nov 6, 2014 at 5:27 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Am Donnerstag, 6. November 2014, 12:44:12 schrieb Brad King:
On
I've put in a fix for this.
580b668d genex: Preserve order while evaluating TARGET_OBJECTS
Can we put this in RC 2?
Clint
- Original Message -
Using the netcdf project
ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-4.3.2.tar.gz
I see a problem with incremental builds doing a relink
An answer to my question
https://stackoverflow.com/questions/5477747/cant-figure-out-how-to-make-swig-java-force-a-proxy-class-to-implement-an-inter
On 5 November 2014 17:28, Witold E Wolski wewol...@gmail.com wrote:
I have some C++ classes which implement an interface.
On the C++ side I
Hi,
I'm setting policy through a file included with NO_POLICY_SCOPE, but
I'm still having trouble with cmake complaining that a policy isn't
set in a particular instance. Is there a way I can dump the policy
stack or might someone have another suggesting on how to debug a
problem where a policy
I thought people on the list might be interested in this blog post:
http://www.kitware.com/blog/home/post/762
Enjoy.
-Bill
--
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
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 562a7b835a21cc395c76fde720f94d0547a6 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 7e884bd6b39776622b1f1a405ac0809125d8205b (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 219b4d57f48d9089f2a12a0503218216eebc2749 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 0f04826ae48f4daf0449383dcf99d1f97d41a6b0 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 621450b6b9a67572e9221406fdf5d8fec530f098 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via a550b6cabe68601bd5e99552bc47b52a92832314 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 6dbb030369553f7ad5f0ca7494d54b3cfb92e9ae (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 06b8c8f9e8b3686b5fc65eaf414d673deb31cc90 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via acc1e1d9662fa132ac1f0f4a5988353dec155a9b (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 76dad3f5e66a5574693d7f43eca9b3b26833c284 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 349e6373ba51ba9280161862e82dcca02d8b5483 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 7cda68d1f7df6b144ade0b7b3011c1e6609b462f (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 84af91f9e53e6f0f5a091e357542b5a255650183 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via e459c5bc57f9ffc784a67ea04d207c1fe0d2f301 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via b67cd9793939d61318794583811d4539a2c12b4b (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via c111642e9d01ccca9b41cdbd84b893081c10be47 (commit)
via
20141106)
+set(CMake_VERSION_PATCH 20141107)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
35 matches
Mail list logo
