https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
Adriaan de Groot <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Adriaan de Groot <[email protected]> --- Please provide the *actual* error messages, instead of paraphrases and re-wordings. That makes it much easier to actually find the problem. The problem lies in ${kpackagetool_cmd}, which is producing that error message (about processor features). Well, not even in kpackagetool, but in QtCore. You could run the tool by hand with /usr/local/bin/kpackagetool5 --appstream-metainfo . --appstream-metainfo-output bogus To see if that runs without producing the same error message. Basically, you've told your build of Qt to only work on processors with feature f16c. If it goes to check, apparently it's not finding that feature. You should be able to trigger the same with QT_NO_CPU_FEATURE=f16c <any qt application>. You might also try building and running this mini-Qt application: === #include <cstdio> #include <QAtomicInteger> extern void qDetectCpuFeatures(); extern QBasicAtomicInteger<quint64> qt_cpu_features[]; int main(int argc, char **argv) { printf("CPU=%lld\n", qt_cpu_features[0].load()); qDetectCpuFeatures(); printf("CPU=%lld\n", qt_cpu_features[0].load()); } === (here I'm assuming you did build Qt as 64 bit library). It should print 0, then possibly crash on you because your Qt library needs features your CPU isn't showing, then a large integer with the features your CPU has. -- You are receiving this mail because: You are the assignee for the bug.
