This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
RFC: Should we link dynamic tests to use the newly built glibc dirctly
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Sat, 6 Oct 2012 16:13:32 -0700
- Subject: RFC: Should we link dynamic tests to use the newly built glibc dirctly
Hi,
The current dynamic tests requires
../ld.so --library-path ...
to run. It isn't easy to run it under gdb. Should we link dynamic tests
to use the newly built glibc directly? Like
gcc -nostdlib -nostartfiles -o
/export/build/gnu/glibc/build-x86_64-linux/string/test-strstr-ifunc
-Wl,-dynamic-linker=/export/build/gnu/glibc/build-x86_64-linux/elf/ld-linux-x86-64.so.2
-Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both
/export/build/gnu/glibc/build-x86_64-linux/csu/crt1.o
/export/build/gnu/glibc/build-x86_64-linux/csu/crti.o `gcc
--print-file-name=crtbegin.o`
/export/build/gnu/glibc/build-x86_64-linux/string/test-strstr-ifunc.o
-Wl,-rpath=/export/build/gnu/glibc/build-x86_64-linux:/export/build/gnu/glibc/build-x86_64-linux/math:/export/build/gnu/glibc/build-x86_64-linux/elf:/export/build/gnu/glibc/build-x86_64-linux/dlfcn:/export/build/gnu/glibc/build-x86_64-linux/nss:/export/build/gnu/glibc/build-x86_64-linux/nis:/export/build/gnu/glibc/build-x86_64-linux/rt:/export/build/gnu/glibc/build-x86_64-linux/resolv:/export/build/gnu/glibc/build-x86_64-linux/crypt:/export/build/gnu/glibc/build-x86_64-linux/nptl
/export/build/gnu/glibc/build-x86_64-linux/libc.so.6
/export/build/gnu/glibc/build-x86_64-linux/libc_nonshared.a
-Wl,--as-needed /export/build/gnu/glibc/build-x86_64-linux/elf/ld.so
-Wl,--no-as-needed -lgcc -Wl,--as-needed -lgcc_s -Wl,--no-as-needed
`gcc --print-file-name=crtend.o`
/export/build/gnu/glibc/build-x86_64-linux/csu/crtn.o
instead of
gcc -nostdlib -nostartfiles -o
/export/build/gnu/glibc/build-x86_64-linux/string/test-strstr-ifunc
-Wl,-dynamic-linker=/lib64/ld-linux-x86-64.so.2 -Wl,-z,combreloc
-Wl,-z,relro -Wl,--hash-style=both
/export/build/gnu/glibc/build-x86_64-linux/csu/crt1.o
/export/build/gnu/glibc/build-x86_64-linux/csu/crti.o `gcc
--print-file-name=crtbegin.o`
/export/build/gnu/glibc/build-x86_64-linux/string/test-strstr-ifunc.o
-Wl,-rpath-link=/export/build/gnu/glibc/build-x86_64-linux:/export/build/gnu/glibc/build-x86_64-linux/math:/export/build/gnu/glibc/build-x86_64-linux/elf:/export/build/gnu/glibc/build-x86_64-linux/dlfcn:/export/build/gnu/glibc/build-x86_64-linux/nss:/export/build/gnu/glibc/build-x86_64-linux/nis:/export/build/gnu/glibc/build-x86_64-linux/rt:/export/build/gnu/glibc/build-x86_64-linux/resolv:/export/build/gnu/glibc/build-x86_64-linux/crypt:/export/build/gnu/glibc/build-x86_64-linux/nptl
/export/build/gnu/glibc/build-x86_64-linux/libc.so.6
/export/build/gnu/glibc/build-x86_64-linux/libc_nonshared.a
-Wl,--as-needed /export/build/gnu/glibc/build-x86_64-linux/elf/ld.so
-Wl,--no-as-needed -lgcc -Wl,--as-needed -lgcc_s -Wl,--no-as-needed
`gcc --print-file-name=crtend.o`
/export/build/gnu/glibc/build-x86_64-linux/csu/crtn.o
Then we can run it under gdb directly.
--
H.J.