I've observed this problem for roughly two or three months. It needs to be fixed for 12.0-RELEASE, IMHO. This seems like it is a package infrastructure issue, since presumably other people are building from ports and not observing this. But perhaps no one else is? I suppose I can try building from ports, but I haven't, because I prefer to use pkg. Bug 231372 may be related, but the reporter indicates they're using 11.1. Steps: * Install any package that uses Qt5 libraries (including KDE) from the official pkg.freebsd.org repository, on a recent 12.0 build. * Attempt to run the binaries built. All the ones I've tried have variations of the following: miranda% gwenview ld-elf.so.1: /usr/local/lib/qt5/libQt5OpenGL.so.5: Undefined symbol "_ZN14QWidgetPrivate14setWindowFlagsE6QFlagsIN2Qt10WindowTypeEE@Qt_5" miranda% okular ld-elf.so.1: /usr/local/lib/qt5/libQt5Network.so.5: Undefined symbol "_ZTI14QObjectPrivate@Qt_5_PRIVATE_API" miranda% quassel ld-elf.so.1: /usr/local/lib/qt5/libQt5DBus.so.5: Undefined symbol "_ZTI14QMetaCallEvent@Qt_5_PRIVATE_API" Environment: FreeBSD miranda.firepipe.net 12.0-ALPHA5 FreeBSD 12.0-ALPHA5 f7e1278b72d(master) amd64 This maps to the following src commit: commit f7e1278b72d533df7e5cd7117c501d1d6bb863aa (HEAD -> master, upstream/master) Author: np <np@FreeBSD.org> Date: Thu Sep 13 22:58:13 2018 +0000 Packages (selected two examples, one without KDE and one with): miranda% pkg info -d quassel quassel-0.12.5_2: qt5-widgets-5.10.1 qt5-gui-5.10.1 qt5-webkit-5.212.0.a2_10 qt5-network-5.10.1 phonon-qt5-4.10.1 qt5-script-5.10.1 qt5-dbus-5.10.1 qt5-core-5.10.1_3 qca-qt5-2.1.3_1 libdbusmenu-qt5-0.9.3.160420160218_5 qt5-sqldrivers-sqlite3-5.10.1 qt5-sql-5.10.1 miranda% pkg info -d gwenview gwenview-18.08.1: qt5-x11extras-5.10.1 libX11-1.6.6,1 kf5-kwindowsystem-5.49.0 kf5-kinit-5.49.0 kf5-kdelibs4support-5.49.0 kf5-kactivities-5.49.0 qt5-widgets-5.10.1 qt5-gui-5.10.1 kf5-kxmlgui-5.49.0 kf5-kwidgetsaddons-5.49.0 kf5-ktextwidgets-5.49.0 kf5-kjobwidgets-5.49.0 kf5-kitemviews-5.49.0 kf5-kconfigwidgets-5.49.0 kf5-kcompletion-5.49.0 kf5-kiconthemes-5.49.0 kf5-kemoticons-5.49.0 qt5-xml-5.10.1 kf5-sonnet-5.49.0 kf5-kcodecs-5.49.0 kf5-baloo-5.49.0 qt5-printsupport-5.10.1 qt5-network-5.10.1 phonon-qt5-4.10.1 qt5-svg-5.10.1 qt5-opengl-5.10.1 png-1.6.35 libkipi-18.08.1 libkdcraw-18.08.1 lcms2-2.9 kf5-kimageformats-5.49.0 jpeg-turbo-2.0.0 exiv2-0.26,1 qt5-dbus-5.10.1 qt5-core-5.10.1_3 qt5-concurrent-5.10.1 kf5-solid-5.49.0 kf5-kservice-5.49.0 kf5-kparts-5.49.0 kf5-knotifications-5.49.0 kf5-kitemmodels-5.49.0 kf5-kio-5.49.0 kf5-ki18n-5.49.0 kf5-kfilemetadata-5.49.0 kf5-kcoreaddons-5.49.0 kf5-kconfig-5.49.0 kf5-kbookmarks-5.49.0 kf5-kauth-5.49.0 kf5-extra-cmake-modules-5.49.0 gettext-runtime-0.19.8.1_1
I don't think it's a package infrastructure issue.
Not sure if it's related, but running keepassxc, I'm now getting: ld-elf.so.1: /usr/local/lib/qt5/plugins/bearer/libqgenericbearer.so: Undefined symbol "_ZN17QNetworkInterfaceC1ERKS_@Qt_5"
On Adrian's suggestion, I decided to delete all my packages, and rm -rf /usr/local/*, and then install them again. I did this manually, though, and only reinstalled the packages I wanted. Now, everything seems to work... I wonder if there are compatibility issues upgrading across some version (libraries are kept for compatibility on upgrade aren't they?), or if you install both Qt4 and Qt5?
@swills: that is the same symbol PR 231402 mentions .. which is a totally weird one.
I'm closing this one as no-longer-reproducible. If wca@ had vlans on the system, then **possibly** this was related to the memory-corruption bug I fixed today (and then fixed-again for 12.0 because IFM_FDDI has gone away).