qt4-mac @4.8.7: configure not detecting arch properly on PPC64

[SerpentChris (Chris Calderon)]

My macports.conf has build arch set to ppc64, and my OS is Mac OS X 10.5.8. At some point during a configure script, things like this start to get printed out a lot, and eventually the build fails.

:info:configure WARNING: Expect ARCH of '-arch ARCH' flag to be exact; got 'ppc64'; ignoring extra.
:info:configure /usr/bin/g++-4.2 -c -pipe -isysroot /Developer/SDKs/MacOSX10.5.sdk -arch ppc64 -O2 -Wall -W  -I../../../mkspecs/macx-g++ -I. -o iconv.o iconv.cpp
:info:configure /usr/bin/g++-4.2 -headerpad_max_install_names -o iconv iconv.o     -Wl,-syslibroot,/Developer/SDKs/MacOSX10.5.sdk -arch ppc -liconv

It looks like the '-arch ppc64' flag is disliked and inconsistently applied.

[kencu (Ken)]

As I recall, qt4 uses some assembly language in it's source files to speed things up. I ran into something like this a year or so ago when I was trying to build it with a specially-made version of clang-3.8 on PPC.

I'd be surprised if you can get it to build ppc64, but I'd be very pleased if it worked in the end!

Ke

[michaelld (Michael Dickens)]

LOL: ​https://www.youtube.com/watch?v=A2eAT2sgISA#t=0m16s

[michaelld (Michael Dickens)]

According to the qt4-mac configure script, "ppc64" is allowed as an arch option, if specified correctly. which we might not be doing since I doubt we've ever had an actual PPC64 available for testing.

[SerpentChris (Chris Calderon)]

I downloaded the source and looked at the configure file, which lead to me believe that setting -arch ppc64 is actually unnecessary, and what really needs to be set is -platform macx-g++-64. I also edited my .profile to export some environmental variables:

export CC=gcc-4.2
export CFLAGS="-m64 -mtune=G5"
export CPPFLAGS="-I/opt/local/include"
export LDFLAGS="-L/opt/local/lib"
export CXX=g++-4.2
export CXXFLAGS=$CFLAGS
export TMPDIR="$HOME/tempdir"

This is the configure line I used, it's basically copied from the output of port -v install, but I removed --jobs=4, -arch "ppc64", and added -host-big-endian -big-endian -platform mac-g++-64:

./configure -v -confirm-license -opensource -prefix /opt/local/libexec/qt4 -bindir /opt/local/libexec/qt4/bin -libdir /opt/local/libexec/qt4/lib -docdir /opt/local/libexec/qt4/share/doc -headerdir /opt/local/libexec/qt4/include -plugindir /opt/local/libexec/qt4/share/plugins -importdir /opt/local/libexec/qt4/share/imports -datadir /opt/local/libexec/qt4/share -translationdir /opt/local/libexec/qt4/share/translations -sysconfdir /opt/local/libexec/qt4/share/sysconf -examplesdir /opt/local/libexec/qt4/share/examples -demosdir /opt/local/libexec/qt4/share/demos -openssl-linked -dbus-linked -fast -no-pch -framework -no-phonon -no-phonon-backend -no-sql-db2 -no-sql-ibase -no-sql-oci -no-sql-tds -no-sql-mysql -no-sql-odbc -no-sql-psql -no-sql-sqlite -no-sql-sqlite2 -nomake demos -nomake examples -release -no-declarative-debug -host-big-endian -big-endian -sdk /Developer/SDKs/MacOSX10.5.sdk -platform macx-g++-64

This compiles qmake with -arch ppc still for some reason, but the configure succeeds and the build goes along and builds everything else with -arch ppc64 until it gets to the file src/gui/dialogs/qfiledialog_mac.mm. When it tries to compile that file, it seems the file is using a part of the Cocoa framework that isn't present in OS X 10.5, specifically the build ends with this message:

gcc-4.2 -c -pipe -O2 -arch ppc64 -Xarch_ppc64 -mmacosx-version-min=10.5 -arch ppc64 -Xarch_ppc64 -mmacosx-version-min=10.5 -fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -isysroot /Developer/SDKs/MacOSX10.5.sdk -DQT_SHARED -DQT_BUILD_GUI_LIB -DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_NO_CUPS -DQT_NO_LPR -DQT_NO_OPENTYPE -DQT_NO_STYLE_WINDOWSVISTA -DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_GTK -DQT_NO_STYLE_WINDOWSCE -DQT_NO_STYLE_WINDOWSMOBILE -DQT_NO_STYLE_S60 -DQ_INTERNAL_QAPP_SRC -DQT_NO_DEBUG -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I../../mkspecs/macx-g++ -I. -I../../include/QtCore -I../../include -I../../include/QtGui -I.rcc/release-shared -Iimage -I../3rdparty/harfbuzz/src -Idialogs -I.moc/release-shared -I.uic/release-shared -F/Users/chris/Downloads/qt-everywhere-opensource-src-4.8.7/lib dialogs/qfiledialog_mac.mm -o .obj/release-shared/qfiledialog_mac.o
dialogs/qfiledialog_mac.mm: In function ‘BOOL -[QNSOpenSavePanelDelegate isHiddenFile:isDir:](QNSOpenSavePanelDelegate*, _message_ref_t*, NSString*, BOOL)’:
dialogs/qfiledialog_mac.mm:300: error: ‘kCFURLIsHiddenKey’ was not declared in this scope
dialogs/qfiledialog_mac.mm:300: error: ‘CFURLCopyResourcePropertyForKey’ was not declared in this scope
gmake[2]: *** [Makefile.Release:16988: .obj/release-shared/qfiledialog_mac.o] Error 1
gmake[2]: Leaving directory '/Users/chris/Downloads/qt-everywhere-opensource-src-4.8.7/src/gui'
gmake[1]: *** [Makefile:34: release] Error 2
gmake[1]: Leaving directory '/Users/chris/Downloads/qt-everywhere-opensource-src-4.8.7/src/gui'
gmake: *** [Makefile:423: sub-gui-make_default-ordered] Error 2

Googling the undeclared things leads to apple developer pages which state they are available in macOS 10.6+. Now I'm not sure what to do. How does it compile without the 64bit platform option? Does it use different code there for some reason?

[kencu (Ken)]

there are a LOT of patches to qt4 to make it work!!

see this one for the issue you noticed, I think:

<​https://github.com/macports/macports-ports/blob/master/aqua/qt4-mac/files/patch-src_gui_dialogs_qfiledialog_mac.mm.diff>

[SerpentChris (Chris Calderon)]

I decided to try applying only that patch and then run the build process again, and it finished. I haven't had a chance to test it yet though.

[michaelld (Michael Dickens)]

This ticket is pretty old, but maybe still relevant for PPC64 builds! Anybody have a chance to test Ken's noted patch not just for build but for actual runtime functionality?

[michaelld (Michael Dickens)]

I'll eventually get one of my older PPC MacOS 10.4 and 10.5 computers going again for testing ... but it might be some time given my workload ...

[barracuda156]

Replying to michaelld:

I'll eventually get one of my older PPC MacOS 10.4 and 10.5 computers going again for testing ... but it might be some time given my workload ...

Any updates? Interested in the result.