vtk @8.2.0_11 +qt5: fails to build on arm/Monterey

[wrohv]

I was previously able to build @8.2.0_10, but now I'm unable to build this variant. Without qt5, the port builds and installs fine.

The +clang13+qt5 variant also didn't build for me initially, but it did successfully build and install after I applied the following patch: ​https://gitlab.kitware.com/vtk/vtk/-/merge_requests/6420/diffs

I also note that the Homebrew formula for vtk contains several lines like this:

  # clang: error: unable to execute command: Segmentation fault: 11
  # clang: error: clang frontend command failed due to signal (use -v to see invocation)
  # Apple clang version 13.1.6 (clang-1316.0.21.2)
  fails_with :clang if DevelopmentTools.clang_build_version == 1316 && Hardware::CPU.arm?

and my system-installed clang version is indeed 13.1.6 (clang-1316.0.21.2)

[ryandesign (Ryan Carsten Schmidt)]

Could you attach the main.log, please?

[wrohv]

Attached. This looks like the relevant part to me:

:info:build clang: error: unable to execute command: Segmentation fault: 11
:info:build clang: error: clang frontend command failed due to signal (use -v to see invocation)
:info:build Apple clang version 13.1.6 (clang-1316.0.21.2)
:info:build Target: arm64-apple-darwin21.4.0

[rdbisme (Ruben Di Battista)]

Replying to wrohv:

Attached. This looks like the relevant part to me:

:info:build clang: error: unable to execute command: Segmentation fault: 11
:info:build clang: error: clang frontend command failed due to signal (use -v to see invocation)
:info:build Apple clang version 13.1.6 (clang-1316.0.21.2)
:info:build Target: arm64-apple-darwin21.4.0

This will be hard for me to test, since I don't have a Mac anymore. My plan was to setup emulation somewhere and keep maintaining these packages, but not sure if I can emulate M1.

I'll try to bump the vtk version somehow and see if they fixed the problem upstream.

[wrohv]

Replying to rdbisme:

This will be hard for me to test, since I don't have a Mac anymore. My plan was to setup emulation somewhere and keep maintaining these packages, but not sure if I can emulate M1.

I'll try to bump the vtk version somehow and see if they fixed the problem upstream.

Just updated to Monterey 12.4 and Xcode 13.4 (clang-1316.0.21.2.5), unfortunately this problem still occurs. I am happy to test any potential fixes on my computer, if you have them.

[wrohv]

Tried again with the latest vtk @9.1.0 +qt5 and Xcode 14 (beta); this combination built successfully for me. Not sure what fixed it as both the Xcode and vtk versions are newer. I initially tried +qt5+clang13, and that failed with a similar error as above but I didn't investigate further after the vanilla +qt5 worked.

Unfortunately, even with the successful build the +qt5 variant didn't produce the correct qt5-enabled vtk library for me. That's a separate issue, and I submitted ​https://github.com/macports/macports-ports/pull/15428 to address that.

With a workable solution to my initial problem, this one can be closed from my perspective.

[mascguy (Christopher Nielsen)]

Replying to wrohv:

Tried again with the latest vtk @9.1.0 +qt5 and Xcode 14 (beta); this combination built successfully for me. Not sure what fixed it as both the Xcode and vtk versions are newer. I initially tried +qt5+clang13, and that failed with a similar error as above but I didn't investigate further after the vanilla +qt5 worked.

Unfortunately, even with the successful build the +qt5 variant didn't produce the correct qt5-enabled vtk library for me. That's a separate issue, and I submitted ​https://github.com/macports/macports-ports/pull/15428 to address that.

With a workable solution to my initial problem, this one can be closed from my perspective.

Glad it's resolved, and thanks again for the PR!