Is it possible to compile a program and include the shared libraries with it?

I dont have root access and I want to install git on my godaddy shared server..

What could work, but is frowned upon, is to build it with shared libs and then put the shared libs into the same directory. If it works, the libs would need to be compatible with the running system.

i tried that but it didnt work. I created my own lib folder and updated the LD_LIBRARY_PATH var and git started to use those shared lib files but i dont want to have to:

run git
upload the missing lib file
run it again
upload another missing file

there are just too many...

Couldn't you compile it all statically linked? If I'm not mistaken, this would build the lib requirements right into the resulting binary, similar to how blackbox works (it has no external dependencies).

Ah thats the term i was looking for. Now to research how to do that.

Thanks!

I would first execute the ./configure script that presumably comes with the git sourcecode, and pass the --help flag to it, like so:

shell# ./configure --help

and look for the option to DISable shared libs, and ENABLE static libs. I've never specifically done this with the intent of making a slandalone binary, but I believe that should do it.

Let us know how it goes

Sasha

awesome thanks sasha

You're welcome -- but don't forget to let us know if it works for future reference.

Cheers!
Sasha

I will later this week

While static link is possible solution it has it's own problems:
1) Not always static libraries exist/available
2) Link command for static linking can be significantly different, than link command for dynamic linking:
- when using dynamic link linker will track dependencies libraries by itself. for static link it's up to programmer to specify all needed libraries.
- for dynamic link libraries can be specified in any order, for static link order is important, and find right one can take time and efforts.
3) Many programs used plugins, i.e them use dlopen to load shared objects in the run time. Examples are any Qt, Gnome progra m and many others.
Even ls (at least when invoked with -l flag) use dlopen
As far as I know there is no way around dlopen (short of redesigning program)

If all mentioned above is not a problem for you, then go to the static link.
If not - there are alternatives.

Executable linked dynamically (as usual) and then used
statifier (http://statifier.sf.net) or
Ermine (http://magicErmine.com)

to convert dynamically linked executable to the self-contained one.

Statifier is licensed under GPL, Ermine - commercial.
On the other hand Ermine works better than statifier on systems with
VDSO/stack randomization

Valery, thank you for stepping in.

I agree, it sounds oversimplified that it will actually work simply via the --static flag and/or through the configuration file.
I'm not much more than an experimenter when it comes to C, but I suspect that `git` will need at the very least, some dlopen's.

Thank you for adding the information you did. I hope it helps the OP

Cheers,
Sasha

If you don't want the hassle, or static linking is not doable, you can better use ldd to determine the whole lot of libraries that you will need, then upload them all at once and launch the program using

If it works, alias it and you are done.

If ldd shows libdl.so - then executable (likely) uses dlopen