On 15 Sep 2001, at 20:57, Frank Heckenbach wrote:
Prof Abimbola Olowofoyeku wrote:
Does GPC link against glibc? I built GPC on a Redhat 7.1 machine and compiled a program there. The program won't run on a Redhat 6.2 machine. It dies with a message "/lib/libc.so.6: version 'GLIBC_2.2' not found ...".
I thought that GPC only links 'libgcc.a'. What gives?
GPC, like almost all programs, links against libc (which provides the interface to the system functions, while libgcc only provides only a few special support routines needed on a platform, such as (I think) 64 bit arithmetic on 32 bit machines).
I see that I've got it all wrong. All the time, I thought that libgcc was *the* C library.
And how can I force GPC to link only to static libraries?
-static
When building GPC, pass it in CFLAGS to make, when compiling programs with GPC, just give it on the command line.
Ok, thanks. Presumably, this means that the binaries will then become much bigger. Does this have any implications for execution speed and /or RAM usage?
Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Author of Chief's Installer Pro for Win32 Email: African_Chief@bigfoot.com http://www.bigfoot.com/~african_chief/