Issues building Slicer on Arch Linux

Development
,
1

Hi everyone, I am having some issues installing slicer and was hoping to get some help…

When I go to build the latest version of Slicer, I get the following error:

In file included from /home/tsims/Documents/Slicer-git/Slicer-SuperBuild-Debug/VTK/Common/DataModel/vtkSphericalPointIterator.cxx:15:
/home/tsims/Documents/Slicer-git/Slicer-SuperBuild-Debug/VTK/Common/DataModel/vtkSphericalPointIterator.h:272:8: error: ‘unique_ptr’ in namespace ‘std’ does not name a template type
  272 |   std::unique_ptr<SphericalPointIterator> Iterator;
      |        ^~~~~~~~~~
/home/tsims/Documents/Slicer-git/Slicer-SuperBuild-Debug/VTK/Common/DataModel/vtkSphericalPointIterator.h:82:1: note: ‘std::unique_ptr’ is defined in header ‘<memory>’; did you forget to ‘#include <memory>’?
   81 | #include "vtkSmartPointer.h" // auto destruct
  +++ |+#include <memory>
   82 |

Adding the #include <memory> statement as the compiler suggests will allow the code to compile, but when running the binary at the end of the process it exits with a address boundary error.

I was wondering if there is a compiler setting or something I’m missing to get this to work?

Thanks in advance!

2

To add some more specifics to the errors I am getting:

running ./Slicer returns

error: [/home/tsims/Documents/Slicer-git/Slicer-SuperBuild-Debug/Slicer-build/bin/./SlicerApp-real] exit abnormally - Report the problem.

And trying to manually run ./bin/SlicerApp-real returns

fish: Job 1, './bin/SlicerApp-real' terminated by signal SIGSEGV (Address boundary error)
3

I had to add the <memory> include in

Modules/Loadable/Markups/MRML/vtkMRMLMarkupsJsonStorageNode_Private.h

Common/DataModel/vtkSphericalPointIterator.h

for a successful build. It’s working flawlessly however, from a clean build. You may trash everything and restart.

4

Thank you so much for your advice! Resetting my local version to the latest changes and running the build again fixed the compilation issue, but it still won’t launch for some reason, giving the same errors as above but that must be something funky on my system.