Sorry for this late answer, I was out of office last week.
I'm building paraview in a cluster running "Rocks Cluster 6.2" distribution. It
is based on CenrOS 6.7
I had some trouble with gcc 4.8.1 (internal error at compile time) so I moved to
Gcc 4.8.5, this is OK now.
My ld version is 2.20.51.0.2-5.43.el6
I use a modified version of OpenMPI 1.7.3 (to work with my batch scheduler)
compiled with gcc 4.8.5.
Setting mesa_USE_SWR to NO as suggested by Ben Boeckel solves the "no such
instruction" problem in building osmesa but my superbuild is still
unsuccessfull. I've now an error in vtkmLevelOfDetail.cxx where I get "undefined
symbols".
The full message is:
[ 27%] Building CXX object
Wrapping/ClientServer/CMakeFiles/vtkFiltersFlowPathsCS.dir/vtkStreamerClientServer.cxx.o
CMakeFiles/vtkAcceleratorsVTKm.dir/vtkmLevelOfDetail.cxx.o: In function `void
vtkm::cont::DynamicArrayHandleBase<vtkm::TypeListTagFieldVec3,
tovtkm::PointListInVTK>::CastAndCall<vtkm::cont::internal::ComputeRange>(vtkm::cont::internal::ComputeRange
const&) const':
vtkmLevelOfDetail.cxx:(.text._ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_[_ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_]+0x160):
undefined reference to `vtkm::cont::ArrayHandle<vtkm::Range,
vtkm::cont::StorageTagBasic>
vtkm::cont::ArrayRangeCompute<vtkm::cont::ArrayHandle<vtkm::Vec<float, 3>,
tovtkm::vtkAOSArrayContainerTag> >(vtkm::cont::ArrayHandle<vtkm::Vec<float, 3>,
tovtkm::vtkAOSArrayContainerTag> const&, vtkm::cont::RuntimeDeviceTracker)'
vtkmLevelOfDetail.cxx:(.text._ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_[_ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_]+0x228):
undefined reference to `vtkm::cont::ArrayHandle<vtkm::Range,
vtkm::cont::StorageTagBasic>
vtkm::cont::ArrayRangeCompute<vtkm::cont::ArrayHandle<vtkm::Vec<double, 3>,
tovtkm::vtkAOSArrayContainerTag> >(vtkm::cont::ArrayHandle<vtkm::Vec<double, 3>,
tovtkm::vtkAOSArrayContainerTag> const&, vtkm::cont::RuntimeDeviceTracker)'
collect2: error: ld returned 1 exit status
My git commit is:
commit 8c380916ea13198b8912bef78971a71bba6d7147
Merge: e75a492 84ebd63
Author: Ben Boeckel <[email protected]>
Date: Tue May 2 12:33:58 2017 +0000
Patrick
Chuck Atkins wrote:
Hi Patrick,
Which OS and Compiler are you using? Also what version of binutils are you
using (`which ld` and `ld --version`)? This is a known issue where the `ld`
shipped with older versions binutils doesn't support the AVX2 instructions
generated for SWR, even though the compiler you're using does. Disabling SWR
isn't really a great option since it's performance is dramatically better than
the llvmpipe alternative. Placing a newer binutils in your path should let
SWR build successfully.
----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.
On Wed, Apr 19, 2017 at 11:47 AM, Patrick Begou
<[email protected]
<mailto:[email protected]>> wrote:
My work to compile paraview 5.3 is in progress but on the cluster (no GPU)
I fail to compile osmesa.
The downloaded tarball is mesa-17.0.1.tar.xz
The message is about invalid instructions:
CXXLD libswrAVX.la
CXX libswrAVX2_la-swr_clear.lo
/tmp/ccDsR3FF.s: Assembler messages:
/tmp/ccDsR3FF.s:109: Error: no such instruction: `shlx %eax,%r8d,%ecx'
/tmp/ccDsR3FF.s:113: Error: no such instruction: `shlx %eax,%r9d,%ecx'
/tmp/ccDsR3FF.s:265: Error: no such instruction: `shlx %eax,%r14d,%edx'
make[5]: *** [libswrAVX2_la-swr_clear.lo] Error 1
I use Python 2.7.9 with mako, gcc (GCC) 4.8.1 and the configure command
generated by paraview-superbuild process in superbuild/osmesa/src is:
./configure --prefix=/kareline/data/begou/PARAVIEW5/build-kareline/install
--enable-opengl --disable-gles1 --disable-gles2 --disable-va
--disable-xvmc --disable-vdpau
--enable-shared-glapi --disable-texture-float --enable-gallium-llvm
--enable-llvm-shared-libs
--with-gallium-drivers=swrast,swr --disable-dri --with-dri-drivers=
--disable-egl --with-egl-platforms=
--disable-gbm --disable-glx
It seams the same as the one provided in the wiki.
I've no idea on how to work around this...
Thanks
Patrick
--
===================================================================
| Equipe M.O.S.T. | |
| Patrick BEGOU | mailto:[email protected]
<mailto:[email protected]> |
| LEGI | |
| BP 53 X | Tel 04 76 82 51 35 |
| 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 |
===================================================================
_______________________________________________
Powered by www.kitware.com <http://www.kitware.com>
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
<http://www.kitware.com/opensource/opensource.html>
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
Search the list archives at: http://markmail.org/search/?q=ParaView
<http://markmail.org/search/?q=ParaView>
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
<http://public.kitware.com/mailman/listinfo/paraview>
--
===================================================================
| Equipe M.O.S.T. | |
| Patrick BEGOU | mailto:[email protected] |
| LEGI | |
| BP 53 X | Tel 04 76 82 51 35 |
| 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 |
===================================================================
_______________________________________________
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 ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
