Backwards compatibility

Andreas Jaeger aj@arthur.rhein-neckar.de
Wed May 26 12:57:00 GMT 1999


>>>>> Jonathan Larmour writes:

Jonathan> Ulrich Drepper wrote:
>> Jonathan Larmour <jlarmour@cygnus.co.uk> writes:
>> 
>> > I had already seen those, but they only talked about libc5<->glibc stuff,
>> > rather than glibc1<->glibc2.
>> 
>> I think what you mean is glibc 2.0 and glibc 2.1?

Jonathan> Sorry yes, that's exactly what I meant. In my closed mind they are the first
Jonathan> and second glibc :-/.

In that case I can help. My glibc2.0.7 tree was configured with
--prefix=/usr/glibc/glibc-2.0.7.

I just use the following long command:
gcc -L /usr/glibc/glibc-2.0.7/lib \
  -I /usr/glibc/glibc-2.0.7/include 
  -Wl,--rpath=/usr/glibc/glibc-2.0.7/lib 
  -Wl,--dynamic-linker=/usr/glibc/glibc-2.0.7/lib/ld-linux.so.2

e.g. 
$ gcc -L /usr/glibc/glibc-2.0.7/lib -I /usr/glibc/glibc-2.0.7/include -Wl,--rpath=/usr/glibc/glibc-2.0.7/lib -Wl,--dynamic-linker=/usr/glibc/glibc-2.0.7/lib/ld-linux.so.2 test_sig.c -lpthread
$ ldd ./a.out 
        libpthread.so.0 => /usr/glibc/glibc-2.0.7/lib/libpthread.so.0 (0x4000d000)
        libc.so.6 => /usr/glibc/glibc-2.0.7/lib/libc.so.6 (0x4001b000)
        /usr/glibc/glibc-2.0.7/lib/ld-linux.so.2 => /usr/glibc/glibc-2.0.7/lib/ld-linux.so.2 (0x40000000)

and the resulting program works just fine.

Andreas
-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de


More information about the Libc-hacker mailing list