https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245946
--- Comment #6 from Kai Knoblich <[email protected]> --- (In reply to Andy Mender from comment #5) Thank you for the updates and no worries about the delayed info regarding the build logs. Meanwhile I also was able to reproduce the issue as reported above by upgrading www/qt5-webengine from 5.14.0 to 5.14.2 via portmaster. My solution was then to remove the previous version of qt5-webengine via "pkg delete -f" and do a "make clean && make install" of the www/qt5-webengine port. Some more technical details for the sake of completeness: If we look at a recent poudriere build log (11.3-RELEASE amd64) [1] there's a small difference with the "-Wl,-rpath-link," parameter in comparison with the outputs from comment #3 and comment #4: > --- ../../libexec/QtWebEngineProcess --- > c++ -B/usr/local/bin -Wl,--as-needed -fstack-protector-strong -pthread > -Wl,-rpath,/usr/local/lib/qt5 > -Wl,-rpath-link,/wrkdirs/usr/ports/www/qt5-webengine/work/.build/lib -o > ../../libexec/QtWebEngineProcess .obj/main.o > -L/wrkdirs/usr/ports/www/qt5-webengine/work/.build/lib -L/usr/local/lib > /usr/local/lib/qt5/libQt5Gui.so /usr/local/lib/qt5/libQt5Core.so -lGL > /wrkdirs/usr/ports/www/qt5-webengine/work/.build/lib/libQt5WebEngineCore.so > /usr/local/lib/qt5/libQt5Quick.so /usr/local/lib/qt5/libQt5QmlModels.so > /usr/local/lib/qt5/libQt5WebChannel.so /usr/local/lib/qt5/libQt5Qml.so > /usr/local/lib/qt5/libQt5Network.so /usr/local/lib/qt5/libQt5Gui.so > /usr/local/lib/qt5/libQt5Positioning.so /usr/local/lib/qt5/libQt5Core.so Within a poudriere build there's no prior version of www/qt5-webengine installed and hence no ldconfig(8) hints file in ${LOCALBASE}/libdata/ldconfig/qt5-webengine exists. The build process then uses its .build/lib/ directory as -rpath-link parameter instead of pointing to ${LOCALBASE}/lib/qt5 . -- [1] http://beefy9.nyi.freebsd.org/data/113amd64-default/533597/logs/qt5-webengine-5.14.2.log -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
