How can I compile a C++ application using GCC so that the binary can be run on multiple Linux distribution? Depending on where I am compiling and where I am running, I get runtime errors about the libc .o file, or files. When I compile code on Linux, the binary is always so small compared to a binary on other systems like Windows or Mac but it looks like that is because very little is being linked into it. Is it possible to link "basic" C/C++ language libraries into the binary? Certain binary-only closed-source programs (like Id Software games for example) seem to function properly across distributions. Sorry if I am missing some fundamental aspect of the Linux architecture. If someone could explain it, I would certainly appreciate it.

-Brandon R

You need to statically link the libraries or add code that makes sure the libraries are present before it tries to run, and takes appropriate action.

gcc usues dynamic linking by default - which is why the binaries are so small compared with those proprietary OS's. It is also the reason for "dependency hell" you may have experienced with rpm installations, and the extensive use of package managers like yum.

Usually, you would want to set up yum, and apt, compatible packages to distribute your software widely. If lots of folk find your work useful, then this will take on a life of its own.

It is not, however, possible to guarantee it will work with every linux distribution possible. There are just too many variables.

Dependency hell is the reason I had to upgrade to Fedora Core 4 instead of just upgrading MySQL.

Well, I think static linking will do. I did some searching before I posted but wasn't looking with the right words. Apparently GCC's -static flag should be just about all I need. I don't plan on distributing packages far and wide, just running off of a flash drive on multiple distros, so this should be the best option.