glibc-2.3 code on glibc-2.2 system?

Hi,

I have a program that I would like to run on my old glibc-2.2 linux (RedHat 7.3) but it requires glibc-2.3. Is there a way to supply those libraries only to that particular program but keep the rest of the system intact? I really want to avoid a full system upgrade (it is a notebook with all my goodies).

I tried using LD_LIBRARY_PATH with a copy of Fedora Core 4 libraries (libc, libpthread), which keeps the linker happy but the program crashes in the end. Also tried adding libm to the list but does not help.

Thanks for any help or pointers,

Denes

P.S: In case it matters, according to ldd, the proggy links against a whole bunch of additional libraries - librt, libXt, libXext, libXmu, libSm, libICE, libX11, libbc, and libdl - but the linker did not complain about these.


.

Relevant Pages

  • Re: Defining many classes in a single file
    ... And one can declare just as many in a header file. ... Another reason for one class one file is due to linker ... smallest resolution. ... In this case, you can have libraries. ...
    (comp.lang.cpp)
  • FreeBSD 5.1 BETA 2 make cvsup-without-gui fails
    ... checking if the linker is GNU ld... ... checking whether the linker supports shared libraries... ... checking if libtool supports shared libraries... ...
    (freebsd-current)
  • Re: orphaned port?
    ... checking if the linker is GNU ld... ... updating cache .././config.cache ... checking if libtool supports shared libraries... ...
    (freebsd-questions)
  • Selective linking of shared libraries.
    ... I am developing an application that uses many executable programs. ... Each of these programs needs to be linked with a variable set of object ... files and shared libraries. ... I know how to instruct the linker to select ...
    (comp.os.linux.development.apps)
  • Re: Coff Object file question
    ... The linker is then handed a bunch of these files. ... Libraries fall into two categories: ... good -- it can then create a final executable file, specifying what ... it specifies the file (e.g. DLL) from which that function is imported. ...
    (alt.lang.asm)