[X2Go-Dev] Bug#973: X2Go issue (in src:x2goclient) has been marked as pending for release

Mihai Moldovan ionic at ionic.de
Mon Jan 18 20:31:14 CET 2016


On 18.01.2016 05:18 PM, David Laxer wrote:
> David-Laxers-MacBook-Pro:x2goclient davidlaxer$ SDK="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk" MACOSX_DEPLOYMENT_TARGET="10.11" ./macbuild.sh
> g++ -c -pipe -stdlib=libc++ -O2 -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.5 -arch i386 -Wall -W -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -DCFGCLIENT -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I../../anaconda/mkspecs/macx-g++ -I../../x2goclient -I../../anaconda/include/QtCore -I../../anaconda/include/QtNetwork -I../../anaconda/include/QtGui -I../../anaconda/include/QtSvg -I../../anaconda/include -I../src -I/opt/local/include -I. -I. -I../../x2goclient -I. -o settingswidget.o ../src/settingswidget.cpp
> clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later)

How did you build Qt4 exactly? Or was it prebuilt?

Looks like my mechanism for passing the deployment target is getting overwritten by qmake by it specifying -mmacosx-version-min=10.5 - the deployment target set at Qt's build time.

If your Qt was built with the 10.5 deployment target, that also entails building it with GCC and libstdc++, which is a very bad choice on anything higher than 10.8 (due to the default C++ standard library - against which all systems libraries also built - being libc++ on these.) I suggest rebuilding it with the deployment target set to 10.11.

Trust me, I know the pains of all of this, being also a MacPorts developer.

For Qt itself and X2Go Client, you're in luck, because neither application links against other C++ libraries and uses the C++ interfaces directly. So you COULD force libstdc++ instead. This, though, means that you must NEVER build software that links to libc++ and this particular Qt version. Doom otherwise.

You're options are:
  1.) Rebuild Qt to use a deployment target of at least 10.8 (preferably 10.11 if you don't plan on distributing binaries) linked against libc++ and build X2GoClient with that. NEVER build an application that links against libstdc++ and against that Qt version. Rebuild all applications that previously linked against that particular Qt version. The last macbuild.sh command you tried should work after that.
  2.) Leave Qt as-is. NEVER build an application that links against libc++ and against that Qt version. Pull the latest changes from our git repository and use SDK="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk" MACOSX_DEPLOYMENT_TARGET="10.5" FORCE_STDLIB="yes" STDLIB="libstdc++" macbuild.sh to build X2Go Client.


The choice is yours.



Mihai

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20160118/ada873b1/attachment.pgp>


More information about the x2go-dev mailing list