Re: glibc 2.2 vs 2.3 issue back again

> The glibc 2.2 vs 2.3 problem came back to haunt me [snip]

> Somebody mentioned in a previous thread (dynamic ELF - > static) that
> all one needs to do is lump together all the dynamic libs needed and use
> LD_LIBRARY_PATH. I know, Paul Pluzhnikov has questioned this and
> probably he is right because it fails for me.
[snip]

> Naively, I would have thought that if I copy all required glibc-2.3
> libraries and all glibc-2.3 version for all the executables (including
> ones executed by the executables themselves), things should be fine.

Gibc considers the PT_INTERP, /lib/ld-linux.so.2, to be an integral part
of glibc. There are mutual dependencies between ld-linux and glibc.

However, you can play by the complete rules, switching the _entire_
glibc package, including ld-linux, for one execve() [command-line process]:
http://BitWagon.com/rtldi/rtldi.html

--

.

Relevant Pages

  • forestalling GNU incompatibility - proposal for binary relative dynamic linking
    ... After spending *two weeks* on various ways of building glibc, ... glibc with fifty patches. ... to a 'standard' out of the box glibc build. ... then the SuSE executables work fine but my new executables break, ...
    (Linux-Kernel)
  • Re: glibc 2.2.5 vs 2.3.2 on RH Enterprise
    ... > All executables on our development machine running RH Enterprise with glibc ... > Short of dynamically linking all the executables and introduce dependency ... use the compat-gcc* packages to insure compatibility ... with the library base of RH 7.3 (glibc 2.2.5). ...
    (comp.os.linux.development.apps)
  • Re: cannot link -static with threads
    ... many people mistakenly believe that static executables are "more ... Glibc compilation results in some 200+ DSOs, ... In order to understand recursion you must first understand recursion. ...
    (comp.programming.threads)
  • glibc 2.2.5 vs 2.3.2 on RH Enterprise
    ... All executables on our development machine runnin RH Enterprise with glibc ... When we installed Enterprise 3 on our test machine ...
    (comp.os.linux.development.apps)
  • Re: Using dlsym for symbols contained in the executable itself
    ... Paul Pluzhnikov wrote: ... dlsym() finds symbols that are in the "dynamic ... You'll find out that PrintAnInt() is not in the dynamic symbol table. ... This is because main executables symbols are not ...
    (comp.unix.programmer)