5.0 RC2 "gmake install" fails on Mac OS X Mountain Lion
-
Installation of my newly built tree fails on OS X Mountain Lion. Any help appreciated!
The source tree is configured thus:
./configure -developer-build -opensource -no-glib -nomake tests
and it builds without errors (if I use -no-glib, otherwise it fails).
When I do this:
sudo gmake install
I get these errors (followed by a number of similar errors):
Undefined symbols for architecture x86_64:
"_CFBundleCopyInfoDictionaryForURL", referenced from:
QFileSystemEngine::bundleName(QFileSystemEntry const&) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
"_CFBundleGetPackageInfoInDirectory", referenced from:
QFileSystemEngine::fillMetaData(QFileSystemEntry const&, QFileSystemMetaData&, QFlagsQFileSystemMetaData::MetaDataFlag) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
"_CFDictionaryGetValue", referenced from:
QFileSystemEngine::bundleName(QFileSystemEntry const&) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
"_CFGetTypeID", referenced from:
QFileSystemEngine::bundleName(QFileSystemEntry const&) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
"_CFRelease", referenced from:
QString::localeAwareCompare_helper(QChar const*, int, QChar const*, int) in libQt5Bootstrap.a(qstring.o)
qt_mac_to_pascal_string(QString, unsigned char*, unsigned int, int) in libQt5Bootstrap.a(qglobal.o)
qt_mac_from_pascal_string(unsigned char const*) in libQt5Bootstrap.a(qglobal.o)
QFileSystemEngine::getLinkTarget(QFileSystemEntry const&, QFileSystemMetaData&) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
QFileSystemEngine::fillMetaData(QFileSystemEntry const&, QFileSystemMetaData&, QFlagsQFileSystemMetaData::MetaDataFlag) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
QFileSystemEngine::canonicalName(QFileSystemEntry const&, QFileSystemMetaData&) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
QFileSystemEngine::bundleName(QFileSystemEntry const&) in libQt5Bootstrap.a(qfilesystemengine_unix.o)
...Thanks in advance!
-
You should not run "make install" for Qt built with -developer-build. This flag means a local, in-source build.
Try using a different linker. g++ works a bit better than ld. Also, consider using make.
-
I see, guess I should have looked up what developer-build actually did. :-)
Thanks for the help!