Linux run file won't run!

Comments

8 comments

  • Avatar
    crubel

    My installers are built with permission 0755 by default on Linux. Only reason I can think of would be something to do with permissions that you have on your projects output directory or something similar.

    Failing that you could always set the file permissions in the Post-Build actions as a last resort.

    0
    Comment actions Permalink
  • Avatar
    jesus

    Windows does not understand Unix permissions, so Unix installers created on Windows will be unpacked without executable permissions and must be manually fixed. It is recommended that you use Unix machines to build the installers as they do not present any limitation.

    0
    Comment actions Permalink
  • Avatar
    crubel

    When you have installbuilder running and your project loaded, if you look at the Customizations section down the left column, then the permissions tab, you will see a section there that allows you to set Unix permissions while building on Windows. The default is 644, have you tried changing this value to something like 755 instead? This seems to indicate that it will do exactly what you want. I have not had the opportunity to try it yet though myself.

    0
    Comment actions Permalink
  • Avatar
    crubel

    Update...

    I made the changes suggested above and it built the Linux installer with Execute permissions on my windows box. So this should take care of it for you.... good luck...

    0
    Comment actions Permalink
  • Avatar
    Gary Turner

    I have the same problem. Were you able to get it to work?

    0
    Comment actions Permalink
  • Avatar
    michiel

    Hi Gary,

    Did you change the permissions of the installer?

        chmod 755 installer.run

    Could you give more details about your build platform and the target platform?

     

    Regards,

    Michiel D'Hont

     

     

    0
    Comment actions Permalink
  • Avatar
    Thomas McDermott

    I had the same problem on my first project, even though permissions were 755 on the run file and my installers had worked fine on Mac OSX and Windows.  The cause might have been uppercase letters in the installer file name:

    1) sudo: ./OpenDSSCmd-1.0-x64-linux-installer.run: command not found

    2) cp OpenDSSCmd-1.0-linux-x64-installer.run test.run

    3) sudo ./test.run

    That third command was successful.  Is this expected?

    Thanks,

    Tom

    0
    Comment actions Permalink
  • Avatar
    BitRock support

    Hi Thomas,

    Yes using uppercase in Linux filenames is probably the cause of the issue. 

    Regards,

    Michiel D'Hont

    0
    Comment actions Permalink

Please sign in to leave a comment.