[<vtk>] build failure
@LilyWangLL is already working on this.
Since Apr 2, 2025.
- Dominant language
- CMake
- Stars
- 27.5k
- Forks
- 7.7k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 321
Description
### Operating system
ubuntu
### Compiler
GCC
### Steps to reproduce the behavior
```Shell
./vcpkg install vtk
```
### Failure logs
In file included from /home/tuobaye/.vcpkg-clion/vcpkg/buildtrees/vtk/src/aed1b438af-abe64eb887.clean/Common/Core/vtkAOSDataArrayTemplate.h:26,
from /home/tuobaye/.vcpkg-clion/vcpkg/buildtrees/vtk/src/aed1b438af-abe64eb887.clean/Common/Core/vtkDoubleArray.h:15,
from /home/tuobaye/.vcpkg-clion/vcpkg/buildtrees/vtk/src/aed1b438af-abe64eb887.clean/Imaging/Hybrid/vtkSampleFunction.cxx:5:
/home/tuobaye/.vcpkg-clion/vcpkg/buildtrees/vtk/src/aed1b438af-abe64eb887.clean/Common/Core/vtkGenericDataArray.h: In instantiation of ‘class vtkGenericDataArray, signed char>’:
/home/tuobaye/.vcpkg-clion/vcpkg/buildtrees/vtk/src/aed1b438af-abe64eb887.clean/Common/Core/vtkAOSDataArrayTemplate.h:32:28: required from ‘class vtkAOSDataArrayTemplate’
/home/tuobaye/.vcpkg-clion/vcpkg/buildtrees/vtk/src/aed1b438af-abe64eb887.clean/Common/Core/vtkAOSDataArrayTemplate.h:341:1: required from here
/home/tuobaye/.vcpkg-clion/vcpkg/buildtrees/vtk/src/aed1b438af-abe64eb887.clean/Common/Core/vtkGenericDataArray.h:136:8: internal compiler error: Segmentation fault
136 | void SetTypedTuple(vtkIdType tupleIdx, const ValueType* tuple)
| ^~~~~~~~~~~~~
0x796c5fe4532f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x796c5fe2a1c9 __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x796c5fe2a28a __libc_start_main_impl
../csu/libc-start.c:360
Please submit a full bug report, with preprocessed source (by using -freport-bug).
Please include the complete backtrace with any bug report.
See for instructions.
### Additional context
can not build vtk and pcl in ubuntu24.04 -clion- vcpkg
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.