On 2004-08-11, Jing-Reng Huang <jrhuang@realtek.com.tw> wrote:
>
>>I seriously doubt it is possible to create a single binary that will run
>>on every system. Even with static compiling, the C libraries and other
>>system libs have changed too much from (for example) Red Hat 7.2 to 9.
If a binary is statically linked it requires *no* libraries. Any
amount of change in the system's libraries will not affect it. Take it
from a guy whose embedded-development forays have forced him to run
statically linked binaries not only on systems with vastly different
system libraries, but also on systems *without* system libraries at
all.
> That's true. I had built static-linked binary packages in Redhat 7.3
> and found it cannot be executed well in RHEL 3 x86 or x86_64.
The only reasons I can imagine for this are: (a) A different binary
format, incompatible with the O/S's loader (which is rather
inconceivable). (b) The binary using some feature not present in the
*kernel*, like a system call that was added or changed in a latter
version, or trying to access a non-existent "/proc" entry, or a
non-existent device node. (c) The compiler producing code for an
uncompatible architecture (CPU) variant. Like, for example, trying to
run a program compiled with "gcc -mcpu=v9 ..." on a system based on a
SPARC-V7 variant.
/npat
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 11 05:37:32 2004