El Miércoles, 4 de Julio de 2007 22:42, Robert Connolly escribió:
> It tests with:
>
> nm $(gcc -print-file-name=libc.a) | grep '__stack_chk_fail' ; echo $?
The libc.a in /tools:
~# nm /tools/lib/libc.a | grep '__stack_chk_fail' ; echo $?
00000000 T __stack_chk_fail
U __stack_chk_fail
00000000 T __stack_chk_fail_local
0
The libc.a instaled in 6.10. Glibc-2.5:
~# nm /mnt/build_dir/usr/lib/static/libc.a | grep '__stack_chk_fail' ; echo $?
00000000 T __stack_chk_fail
U __stack_chk_fail
00000000 T __stack_chk_fail_local
0
but
configure:16234: checking __stack_chk_fail in target GNU C library
configure:16247: result: no
Maybe that is due we are moving libc.a to /usr/lib/static/ after
installation ??
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info
TLDP-ES: http://es.tldp.org
--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
