Re: [Paraview] [Non-DoD Source] Building on Cray systems

view" <paraview@paraview.org>, "Chuck Atkins" <chuck.atk...@kitware.com> Sent: Thursday, February 25, 2016 11:44:28 AM Subject: Re: [Paraview] [Non-DoD Source] Building on Cray systems Hi Tim, Yep, you did update the list a while ago. I just wanted to make su

Re: [Paraview] [Non-DoD Source] Building on Cray systems

quot;paraview" <paraview@paraview.org>, "Chuck Atkins" <chuck.atk...@kitware.com> Sent: Thursday, February 25, 2016 11:44:28 AM Subject: Re: [Paraview] [Non-DoD Source] Building on Cray systems Hi Tim, Yep, you did update the list a while ago. I just

Re: [Paraview] [Non-DoD Source] Building on Cray systems

*"Andy Bauer" <andy.ba...@kitware.com> > *To: *"Chuck Atkins" <chuck.atk...@kitware.com> > *Cc: *"tim gallagher" <tim.gallag...@gatech.edu>, "paraview" < > paraview@paraview.org> > *Sent: *Thursday, February 25, 2016 11:21:27 AM &

Re: [Paraview] [Non-DoD Source] Building on Cray systems

> To: "Chuck Atkins" <chuck.atk...@kitware.com> Cc: "tim gallagher" <tim.gallag...@gatech.edu>, "paraview" <paraview@paraview.org> Sent: Thursday, February 25, 2016 11:21:27 AM Subject: Re: [Paraview] [Non-DoD Source] Building on Cray systems

Re: [Paraview] [Non-DoD Source] Building on Cray systems

Hi Tim, Were you able to get Catalyst built on any of those machines? I briefly tried on Copper and Garnet with the superbuild but hit some failure that I didn't investigate further. Best, Andy On Mon, Feb 8, 2016 at 2:51 PM, Chuck Atkins wrote: > Hi Tim, > > When

Re: [Paraview] [Non-DoD Source] Building on Cray systems

Hi Tim, When building CMake on a Cray, you'll want to build using the host system compilers, i.e. /usr/bin/gcc and /usr/bin/g++, not with the cray compiler wrappers. Usually I just do: module purge CC=/usr/bin/gcc CXX=/usr/bin/g++ /path/to/cmake_source/bootstrap --prefix=/path/to/cmake/install

Re: [Paraview] [Non-DoD Source] Building on Cray systems

Sorry if you get this multiple times -- the original was blocked from the PV list because the output log was too big. I can send the log I referred to off-list to anybody who is interested. -- Good morning! Thanks Andy and Richard for the

Re: [Paraview] [Non-DoD Source] Building on Cray systems

of these systems - there are >> modules available to load various version of Paraview.If you need to >> do >> your own builds to support specific functionality - I can provide you the >> build scripts we use on those systems. >> >> >> >>

Re: [Paraview] [Non-DoD Source] Building on Cray systems

: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Tim Gallagher Sent: Thursday, February 04, 2016 8:25 AM To: paraview <paraview@paraview.org> Subject: [Non-DoD Source] [Paraview] Building on Cray systems All active links contained in this email were disabled. Please verify the id

Re: [Paraview] [Non-DoD Source] Building on Cray systems

- From: "Richard C Angelini (Rick) CIV USARMY RDECOM ARL (US)" <richard.c.angelini@mail.mil> To: "tim gallagher" <tim.gallag...@gatech.edu>, "paraview" <paraview@paraview.org> Sent: Thursday, February 4, 2016 8:54:08 AM Subject: RE: [Non-DoD

Re: [Paraview] [Non-DoD Source] Building on Cray systems

elini@mail.mil> Cc: "tim gallagher" <tim.gallag...@gatech.edu>, "paraview" <paraview@paraview.org> Sent: Thursday, February 4, 2016 9:15:03 AM Subject: Re: [Paraview] [Non-DoD Source] Building on Cray systems Hi Rick, Did you build ParaView with PARAVIEW_

Re: [Paraview] [Non-DoD Source] Building on Cray systems

, February 04, 2016 8:25 AM > To: paraview <paraview@paraview.org> > Subject: [Non-DoD Source] [Paraview] Building on Cray systems > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm the authenticity of all links containe

Re: [Paraview] [Non-DoD Source] Building on Cray systems

stems. -Original Message- From: ParaView [Caution-mailto:paraview-boun...@paraview.org < Caution-mailto:paraview-boun...@paraview.org > ] On Behalf Of Tim Gallagher Sent: Thursday, February 04, 2016 8:25 AM To: paraview <paraview@paraview.org<mailto:paraview@paraview.org> < Caution