Yet another victim of static linking on Linux. :/

The short answer is, don't.

It's far easier to distribute a set of .so files and set LD_LIBRARY_PATH at runtime to load them.

Otherwise, you're in for a heap of hurt. There is no such thing as a fully statically linked executable in Linux due to all the different library versions available that have to be linked dynamically.

Or give users a script that installs the dependencies for you before first run.

There was a talk about this on IRC and there is another solution I can't remember at the moment. Someone please chime in here. It allowed you to distribute a single file to multiple distros.

It's not the linking causing the seg fault, it's your code, likely the current working directory is wrong when run from inside code blocks.

You can set the project cwd with the following; Go to Menu->Project->Build Settings->Executable working directory and change it.

Then your program will find your runtime dependencies.

You can also fix your program by setting the cwd programmatically.

Try a debugger like gdb. It will tell you exactly why it is throwing a seg fault.

Commonly you add your env to the library path just before launching, like:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/your/custom/path/

In a .sh script, admitting you put all the .so in a lib directory:

#!/bin/sh
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:./lib/
./my_super_binary -o my_options_if_any
exit $?  #return the launched proc exit code

Edit:
Don't forget to chmod +x or +X , and ./my_script.sh to start with the good env

I don't know. I never use it or see it a lot.