Opened 14 months ago
Closed 14 months ago
#68219 closed defect (fixed)
qt5-qtbase @5.15.10_1: dyld: Symbol not found: __ZNSt3__13pmr15memory_resourceD2Ev
Reported by: | chrstphrchvz (Christopher Chavez) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | ||
Port: | qt5-qtbase |
Description
Building with the macOS 14.0 SDK (from Xcode 15 command line tools) on macOS 13 Ventura encounters a runtime linker error:
/opt/local/var/macports/build/_opt_local_var_macports_sources_mse.uk.rsync.macports.org_rsync.macports.org_release_tarballs_ports_aqua_qt5/qt5-qtbase/work/qtbase-everywhere-src-5.15.10/src/gui/qvkgen_wrapper.sh vulkan/vk.xml /opt/local/var/macports/build/_opt_local_var_macports_sources_mse.uk.rsync.macports.org_rsync.macports.org_release_tarballs_ports_aqua_qt5/qt5-qtbase/work/qtbase-everywhere-src-5.15.10/header.LGPL vulkan/qvulkanfunctions dyld[69446]: Symbol not found: __ZNSt3__13pmr15memory_resourceD2Ev Referenced from: <CB507A0E-7858-358A-A4C4-D8023DF6627A> /opt/local/var/macports/build/_opt_local_var_macports_sources_mse.uk.rsync.macports.org_rsync.macports.org_release_tarballs_ports_aqua_qt5/qt5-qtbase/work/qtbase-everywhere-src-5.15.10/lib/QtCore.framework/Versions/5/QtCore Expected in: <8B258FAF-4392-3385-A019-D80F49C5AF31> /usr/lib/libc++.1.dylib make[2]: *** [vulkan/qvulkanfunctions.h] Abort trap: 6
It seems similar to #67980 where the build is erroneously assuming runtime availability of C++17 <memory_resource>
, which is not the case before macOS 14 Sonoma. I am not aware if this vulkan-related target is supposed to be built despite intentionally passing -no-feature-vulkan
to configure.
Using configure.sdk_version=13.3
fails to work around the issue, apparently because some steps use -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
, which now points to MacOSX14.0.sdk; maybe this is due to -sdk macosx
being intentionally passed to the configure script to avoid hardcoding a specific SDK version in installed files.
Change History (4)
comment:1 Changed 14 months ago by chrstphrchvz (Christopher Chavez)
comment:2 follow-up: 3 Changed 14 months ago by devernay (Frédéric Devernay)
Is this intel-specific? I didn't have this issue when building qt5 on a M1 mac with Ventura.
comment:3 Changed 14 months ago by chrstphrchvz (Christopher Chavez)
Replying to devernay:
Is this intel-specific? I didn't have this issue when building qt5 on a M1 mac with Ventura.
I don’t suspect that this is Intel-specific. Could it be that your system installed qt5-qtbase @5.15.10_1 from the binary archive (which is the default behavior when a binary archive is available) rather than from source? MacPorts’ macOS 13 builder will not encounter this problem since it will not have the macOS 14 SDK.
comment:4 Changed 14 months ago by chrstphrchvz (Christopher Chavez)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Backporting the fix for #67980 seems to work. https://github.com/macports/macports-ports/pull/20538