Ask / Submit

After Sailfish SDK 1407 update build complains about /home/src1 and fails

asked 2014-07-16 10:00:37 +0300

skubo gravatar image

updated 2014-07-16 12:45:13 +0300

kaltsi gravatar image

The latest SDK update killed my apps build (outputting "/home/src1 is a directory", make failed)

I had to remove the SDK toolkit, manually delete /home/<user>/.config/SailfishAlpha4 and re-install to make it working again.

edit retag flag offensive close delete


Did you close Qt Creator during the update? Did you first try only removing the ~/.config/SailfishAlpha4 directory or did it really require the full reinstall? When removing the SailfishAlpha4 directory it is necessary to first close Qt Creator, then remove the dir and then restart Qt Creator.

kaltsi ( 2014-07-16 11:16:30 +0300 )edit

Yes, I did close Qt Creator. I don't know however, if there was a background process still dangling or not. And no, I did not try removing the folder first before re-install, but you're right that probably might have fixed it without re-install

skubo ( 2014-07-16 11:27:24 +0300 )edit

I have the same problem with Linux. I started Qt Creator, selected "update" in help menu and started the update. After the first action of the updater it restarted itself and I continued the updater _without_ closing the Qt Creator. The updater then told me to close QT Creator. Then the updating could be continued.

Removing only ~/.config/SailfishAlpha4 is not sufficient to solve the problem.

ibins ( 2014-07-16 11:32:21 +0300 )edit

Did either of you have the "alternate source folder" configured with the previous SDK? The installer asks for it or it can be changed from Mer settings later. If you had it configured, does that folder path exist in your current environment?

kaltsi ( 2014-07-16 11:43:31 +0300 )edit

I think I had it configured to "/home/<user>/something ; and yes, the "something" exists.

skubo ( 2014-07-16 11:50:53 +0300 )edit

4 Answers

Sort by » oldest newest most voted

answered 2014-07-16 10:59:10 +0300

kaltsi gravatar image

updated 2014-07-17 11:55:58 +0300

We ran into this problem once during internal testing, but were unable to figure out what could have been the cause. Thanks for the report, we'll try to figure it out.


Now I understand the cause for this problem. If the alternate project folder is changed from the Qt Creator options after installation, that new value is not set correctly by the update process to the MerSDK virtual machine.

An example:

1) user installed the 1406 SDK and didn't select the alternate project folder in the installer, so it defaults to /home/user. Later he changes it to /opt and continues hacking happily.

2) upgrade dialog to 1407 pops up and user chooses to upgrade the SDK. The upgrade first removes the old MerSDK and recreates it using the new data from the upgrade. Unfortunately the upgrade process is unaware that the user has changed the alternate project folder to /opt and recreates MerSDK with the original value of /home/user.

Now Qt Creator thinks that the alt project folder is /opt and happily opens projects from there, but MerSDK thinks it's /home/user and when it tries to start building the project it cannot find the files from the correct place.

One way to fix it is to reinstall, the less destructive way to fix it is to set the alternate project folder from Qt Creator options first to /tmp and then back to /opt. This way MerSDK will be reconfigured to use the correct alt project folder.

Sorry for the bug, it was a case that was not properly tested. It is also non trivial to fix properly, but we'll figure out something.

edit flag offensive delete publish link more



FWIW, I did just hit what seems to be this issue with the current (Beta) release: 1506-Qt5 on a fresh install with a fresh user, though I'm not quite sure what the exact sequence of events was leading to this. Even so, setting the alternate project folder (to the same as the project folder) has fixed it for me.

FrederikF ( 2015-08-29 23:34:48 +0300 )edit

answered 2014-07-16 12:50:14 +0300

ibins gravatar image

The shared folder setting for the Mer Virtual Machine was corrupt after the update. The slash between the ~ and the project directory was missing. Solution:

  • Stop all virtual machines
  • enter the correct path to your project in "Extras -> Settings (last menu item) -> tab "Mer" -> text field "Alt source folder"
edit flag offensive delete publish link more


What had you entered there originally? Was it just ~ or ~/somedir ?

kaltsi ( 2014-07-16 13:04:47 +0300 )edit

It was ~somedir instead of ~/somedir, the slash was missing, the whole string was red coloured (invalid)

ibins ( 2014-07-16 14:10:08 +0300 )edit

Correct place in the latest SDK is Tools -> Options... -> Mer -> Shared folders -> Browse. Note that after selecting a valid folder you have to press the Change button! Pressing Apply or OK of the Options window itself is not enough.

andyn ( 2016-07-18 23:37:18 +0300 )edit

answered 2016-02-08 06:34:13 +0300

Got this issue, when deleted Alt Source Folder. It will be nice to see "Mer Alt Source Folder not found" except of "/home/src1 is a directory"

edit flag offensive delete publish link more

answered 2017-07-09 19:30:00 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2017-07-09 19:30:00 +0300

To fix it, setting change in the gui didn't change anything, for me : sudo ln -s /home/myuser/ /home/src1

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2014-07-16 10:00:37 +0300

Seen: 741 times

Last updated: Jul 09 '17