[Paraview] Error cross-compiling Catalyst on BG/Q

[Biddiscombe, John A.]

Rich

On the BGQ, the compute nodes and login nodes are binary compatible, so you shouldn’t need to bother with most of the cross compiling stuff. the only thing to watch out for is the MPI and since vtkParseOGLExt and vtkWrapPython etc don’t touch that, you ought to be ok compiling
_as if_ you were going to run on the host node. If you use the MPI wrappers (I don’t), then all will be taken care of.

I don’t think that I have compiled pv+catalyst to run on BGQ, so my comment is only based on theory, but I can set a build going in a minute if it helps (except I’d need to setup mesa which may take a while, so maybe I won’t....)

JB


From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle
Sent: 13 February 2015 01:19
To: Cook, Rich
Cc: ParaView list
Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q


On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich <cook47 at llnl.gov<mailto:cook47 at llnl.gov>> wrote:
/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT

Is the name of the executable to run.

set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT
     "PLEASE_FILL_OUT-FAILED_TO_RUN"
     CACHE STRING "Result from TRY_RUN" FORCE)

Change that to:
set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT
     0
     CACHE STRING "Result from TRY_RUN" FORCE)

if the return code of that executable is 0

set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT
     "PLEASE_FILL_OUT-NOTFOUND"
     CACHE STRING "Output from TRY_RUN" FORCE)

Change that to:
set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT
     "I am the very model of a modern major general"
     CACHE STRING "Output from TRY_RUN" FORCE)

If the console output of that executable was "I am the very model of a modern major general"

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150213/b43780c6/attachment.html>