Bug#1072939: paraview: armel needs -latomic linking

Drew Parsons dparsons at debian.org
Mon Jun 10 17:12:23 BST 2024


Package: paraview
Version: 5.12.0+dfsg-4
Severity: important
Control: forwarded -1 https://gitlab.kitware.com/vtk/vtk/-/issues/19352


paraview FTBFS on armel with 

bin/vtkWrapPython-pv5.12 -MF /<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkRemotingServerManagerPython/vtkSMDataSourceProxyPython.cxx.d @/<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkRemotingServerManagerPython/vtkRemotingServerManager-python.DEBUG.args -o /<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkRemotingServerManagerPython/vtkSMDataSourceProxyPython.cxx /<<PKGBUILDDIR>>/Remoting/ServerManager/vtkSMDataSourceProxy.h
[ 79%] Building CXX object CMakeFiles/vtkRenderingOpenGL2CS.dir/CMakeFiles/vtkRenderingOpenGL2CS/vtkClearRGBPassClientServer.cxx.o
[ 79%] Generating Python wrapper sources for vtkOpenGLRenderer
bin/vtkWrapPython-pv5.12 -MF /<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkRenderingOpenGL2Python/vtkOpenGLRendererPython.cxx.d @/<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkRenderingOpenGL2Python/vtkRenderingOpenGL2-python.DEBUG.args -o /<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkRenderingOpenGL2Python/vtkOpenGLRendererPython.cxx /<<PKGBUILDDIR>>/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.h
/usr/bin/c++ -Dkiss_fft_scalar=double -DvtkRenderingCore_AUTOINIT_INCLUDE=\"/<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkModuleAutoInit_5e984c86b020da752eb6357425f4f168.h\" -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Rendering/OpenGL2 -I/<<PKGBUILDDIR>>/VTK/Rendering/OpenGL2 -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Common/Core -I/<<PKGBUILDDIR>>/VTK/Common/Core -I/<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/token/vtktoken/token -I/<<PKGBUILDDIR>>/VTK/ThirdParty/token/vtktoken/token -I/<<PKGBUILDDIR>>/VTK/ThirdParty/token/vtktoken -I/<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/token/vtktoken -I/<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/nlohmannjson/vtknlohmannjson -I/<<PKGBUILDDIR>>/VTK/ThirdParty/nlohmannjson/vtknlohmannjson -I/<<PKGBUILDDIR>>/VTK/ThirdParty/nlohmannjson/vtknlohmannjson/include -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Common/DataModel -I/<<PKGBUILDDIR>>/VTK/Common/DataModel -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Common/Math -I/<<PKGBUILDDIR>>/VTK/Common/Math -I/<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/kissfft/vtkkissfft -I/<<PKGBUILDDIR>>/VTK/ThirdParty/kissfft/vtkkissfft -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Common/Transforms -I/<<PKGBUILDDIR>>/VTK/Common/Transforms -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Filters/General -I/<<PKGBUILDDIR>>/VTK/Filters/General -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Common/ExecutionModel -I/<<PKGBUILDDIR>>/VTK/Common/ExecutionModel -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Common/Misc -I/<<PKGBUILDDIR>>/VTK/Common/Misc -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Filters/Core -I/<<PKGBUILDDIR>>/VTK/Filters/Core -I/<<PKGBUILDDIR>>/build.python3.12/VTK/IO/Image -I/<<PKGBUILDDIR>>/VTK/IO/Image -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Imaging/Core -I/<<PKGBUILDDIR>>/VTK/Imaging/Core -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Rendering/Core -I/<<PKGBUILDDIR>>/VTK/Rendering/Core -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Rendering/HyperTreeGrid -I/<<PKGBUILDDIR>>/VTK/Rendering/HyperTreeGrid -I/<<PKGBUILDDIR>>/build.python3.12/VTK/Rendering/UI -I/<<PKGBUILDDIR>>/VTK/Rendering/UI -I/<<PKGBUILDDIR>>/build.python3.12/Remoting/ClientServerStream -I/<<PKGBUILDDIR>>/Remoting/ClientServerStream -isystem /<<PKGBUILDDIR>>/build.python3.12/VTK/Utilities/KWIML -isystem /<<PKGBUILDDIR>>/VTK/Utilities/KWIML -isystem /<<PKGBUILDDIR>>/build.python3.12/VTK/Utilities/KWSys -isystem /<<PKGBUILDDIR>>/VTK/Utilities/KWSys -isystem /<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/token -isystem /<<PKGBUILDDIR>>/VTK/ThirdParty/token -isystem /<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/nlohmannjson -isystem /<<PKGBUILDDIR>>/VTK/ThirdParty/nlohmannjson -isystem /<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/kissfft -isystem /<<PKGBUILDDIR>>/VTK/ThirdParty/kissfft -isystem /<<PKGBUILDDIR>>/build.python3.12/VTK/ThirdParty/glew -isystem /<<PKGBUILDDIR>>/VTK/ThirdParty/glew -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -O0  -g -std=c++11 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT CMakeFiles/vtkRenderingOpenGL2CS.dir/CMakeFiles/vtkRenderingOpenGL2CS/vtkClearRGBPassClientServer.cxx.o -MF CMakeFiles/vtkRenderingOpenGL2CS.dir/CMakeFiles/vtkRenderingOpenGL2CS/vtkClearRGBPassClientServer.cxx.o.d -o CMakeFiles/vtkRenderingOpenGL2CS.dir/CMakeFiles/vtkRenderingOpenGL2CS/vtkClearRGBPassClientServer.cxx.o -c /<<PKGBUILDDIR>>/build.python3.12/CMakeFiles/vtkRenderingOpenGL2CS/vtkClearRGBPassClientServer.cxx
/usr/bin/ld: ../../../lib/arm-linux-gnueabi/libvtkCommonDataModel-pv5.12.so.5.12: undefined reference to `__atomic_fetch_add_8'
[ 79%] Generating Python wrapper sources for vtkSMDataTypeDomain
collect2: error: ld returned 1 exit status


see
https://buildd.debian.org/status/fetch.php?pkg=paraview&arch=armel&ver=5.12.1%2Bdfsg-2&stamp=1718029171&raw=0

The problem with atomics is discussed upstream (VTK) at
https://gitlab.kitware.com/vtk/vtk/-/issues/19352

see also
https://gitlab.kitware.com/cmake/cmake/-/issues/23021
https://github.com/google/highway/pull/1008/files

Should be fixed in the toolchain (gcc) not in applications.
in the meantime probably best for paraview to follow the VTK patch
https://salsa.debian.org/science-team/vtk9/-/merge_requests/1



More information about the debian-science-maintainers mailing list