Ask / Submit

SailfishOS SDK installation fails on OSX 10.6.8

asked 2015-03-01 19:43:50 +0200

MaxR gravatar image

Just like Kim, the installation of the SailfishOS SDK fails on my computer, which is running Mac OS X 10.6.8. During the installation, I have the same message than him popping up:

Error during the installation process (org.merproject.mersdk): The execution failed (crash) : "/Users/Maxou/SailfishOS/bin/ '/Users/Maxou/SailfishOS/vmshare/ssh/private_keys/engine/root' '/Users/Maxou/SailfishOS/vmshare/ssh/private_keys/engine/'"

Following Ove's advices posted in SailfishOS SDK installation fails (answered), I tried to run the installer with my Airport deactivated, as it seems to have solve the problem for Kim, but it does not for me.

Is there any chance someone encountered the same problem with a mac, and found a way to solve it?

Here's my config: Macbook pro Mid/Late 2007, Mac OS X 10.6.8, 2.2 GHz Intel Core 2 Duo, 4 Go 667 ...DR2 SDRAM And I have about 250 Go of free memory on my hard drive.

edit retag flag offensive close delete


Maybe a stupid question (not a Mac user myself), but why don't you upgrade to a newer release of OS X? According to Wikipedia your laptop is supported by the latest release (10.10) which is free from Apple :)

Louis ( 2015-03-02 05:38:46 +0200 )edit

Several reasons, mostly because I really don't appreciate their new design, and also because it seems to consume much more RAM than before, and this is not something I can upgrade for free.

MaxR ( 2015-03-03 13:55:31 +0200 )edit

2 Answers

Sort by » oldest newest most voted

answered 2015-03-03 19:06:58 +0200

Jare gravatar image

A while ago we did some further digging on this matter and found out it might not be as easy as disabling C++11 on Qt 5.2.1 compilation. Specifically there's one post from qt-project mailing list ( It states that you would need to compile on OS X 10.6, if you want to include QtWebkit. And QtWebkit is used in the IDE, so it cannot be dropped out. For further testing we would need a Mac with OS X 10.6, but at the same time you have to remember that 10.6 is an outdated OS that isn't supported by Apple since February 2014. And also Qt project is moving towards supporting only OS X 10.7+:

edit flag offensive delete publish link more


Bummer! Thanks for the update though! I can help out with that if needed, maybe a transplant can be made somehow? I also have no good excuse to still be on this underpowered laptop, however OS X went seriously downhill from here. Although rumor has it it's gotten better again (I haven't checked the last two really). Tried the new version just now, still keeps crashing every which way during installation. Did you in fact build without C++11? Seems odd to me QtWebKit would be used during installation.

attah ( 2015-03-03 23:27:59 +0200 )edit

Ok, I guess this ends the discussion then. Thanks anyway, and keep up with the good work!

MaxR ( 2015-04-05 12:13:02 +0200 )edit

answered 2015-03-01 20:29:11 +0200

attah gravatar image

updated 2015-03-01 20:36:46 +0200


I'm on 10.6 as well, and have had this for quite some time now. This is because Qt nowadays uses C++11, and thus depends on libcxx instead of (only?) libstdc++, which isn't present on 10.6. I'm 99% sure that it's the issue, all googling of error messages points to this. Not the one you are seeing, but the crash reports from the OS.. although i recognize that error from the installer.

I have reported it to Jolla dev care back in December, and this is the answer I got:

Reply from our SDK team:

“Thank you for your report. We'll check this out for the future SDK releases. Unfortunately the release process for the current one was too far away for it to be thoroughly tested and perhaps included in it.”

(I suggested what seems to be the most common workaround for other Qt projects, disabling C++11)

The current they are referring to is the U10 SDK, so the one we have now.

So it seems we are out of luck until maybe the next version.

edit flag offensive delete publish link more



Thanks for your answer, I hope they will be able to sort this out at jolla for the next release. As we're using an old Mac OS X, I guess we're bound to encounter more problems than others.

If you find a workaround, I'll be pleased to hear about it, and I'll make sure to do the same.

MaxR ( 2015-03-01 20:57:32 +0200 )edit

Fwiw I tried building my own libcxx (I'm told that's a bad thing to do at lest if i want my macports to keep working). Then i got a whole host of other errors, and gave up.

attah ( 2015-03-01 22:40:02 +0200 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2015-03-01 19:43:50 +0200

Seen: 177 times

Last updated: Mar 01 '15