OSX/CI: ?NEW? qt5 build failure !!!
Marko Käning
mk-lists at email.de
Tue Aug 12 18:22:09 UTC 2014
Hi Ben and FW folks,
suddenly I can’t build *qt5* on my OSX/CI VM anymore! :-(
As there are quite a few errors in the log, I attached it to this post.
Many of them might come from the configure phase, I guess.
The last error shown is this:
---
Undefined symbols for architecture x86_64:
"QMacTimeZonePrivate::QMacTimeZonePrivate(QByteArray const&)", referenced from:
newBackendTimeZone(QByteArray const&) in qtimezone.o
"QMacTimeZonePrivate::QMacTimeZonePrivate()", referenced from:
newBackendTimeZone() in qtimezone.o
"QFseventsFileSystemWatcherEngine::removePaths(QStringList const&, QStringList*, QStringList*)", referenced from:
vtable for QFseventsFileSystemWatcherEngine in moc_qfilesystemwatcher_fsevents_p.o
"QFseventsFileSystemWatcherEngine::restartStream()", referenced from:
QFseventsFileSystemWatcherEngine::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in moc_qfilesystemwatcher_fsevents_p.o
"QFseventsFileSystemWatcherEngine::doEmitFileChanged(QString, bool)", referenced from:
QFseventsFileSystemWatcherEngine::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in moc_qfilesystemwatcher_fsevents_p.o
"QFseventsFileSystemWatcherEngine::doEmitFileChanged(QString, bool)", referenced from:
QFseventsFileSystemWatcherEngine::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in moc_qfilesystemwatcher_fsevents_p.o
"QFseventsFileSystemWatcherEngine::doEmitDirectoryChanged(QString, bool)", referenced from:
QFseventsFileSystemWatcherEngine::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in moc_qfilesystemwatcher_fsevents_p.o
"QFseventsFileSystemWatcherEngine::create(QObject*)", referenced from:
QFileSystemWatcherPrivate::createNativeEngine(QObject*) in qfilesystemwatcher.o
"QFseventsFileSystemWatcherEngine::addPaths(QStringList const&, QStringList*, QStringList*)", referenced from:
vtable for QFseventsFileSystemWatcherEngine in moc_qfilesystemwatcher_fsevents_p.o
"QFseventsFileSystemWatcherEngine::~QFseventsFileSystemWatcherEngine()", referenced from:
vtable for QFseventsFileSystemWatcherEngine in moc_qfilesystemwatcher_fsevents_p.o
"QFseventsFileSystemWatcherEngine::~QFseventsFileSystemWatcherEngine()", referenced from:
vtable for QFseventsFileSystemWatcherEngine in moc_qfilesystemwatcher_fsevents_p.o
"QSystemLocale::fallbackUiLocale() const", referenced from:
vtable for QSystemLocale in qlocale.o
vtable for QSystemLocaleSingleton in qlocale.o
"QSystemLocale::query(QSystemLocale::QueryType, QVariant) const", referenced from:
vtable for QSystemLocale in qlocale.o
vtable for QSystemLocaleSingleton in qlocale.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [../../lib/libQt5Core_debug.5.3.1.dylib] Error 1
make[2]: *** [sub-corelib-make_first] Error 2
make[1]: *** [sub-src-make_first] Error 2
make: *** [module-qtbase-make_first] Error 2
KDE Continuous Integration Build
== Building Project: qt5 - Branch stable
---
As I haven’t rebuilt qt5 for _quite_some_time_ it looks like that this is a new issue which hadn’t been detected up to now on OSX…
Could that be?
Or did I mess up somewhere myself?
Greets,
Marko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt5.log.gz
Type: application/x-gzip
Size: 27471 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140812/2f625e54/attachment-0001.gz>
More information about the Kde-frameworks-devel
mailing list