PB> No, though strip --strip-debug might do the trick. Or you could compile glibc
PB> with --enable-omitfp. Unless disk space is very short I wouldn't recommend
PB> trying to get rid of the debug information though.
Hm. Why just plain strip will not work ? Al least here this looks ok:
-- cut --
[root@localhost /lib]# ls -al libc-2.0.7.so
-rwxr-xr-x 1 root root 3061550 May 10 1998 libc-2.0.7.so
[root@localhost /lib]# strip libc-2.0.7.so
[root@localhost /lib]# ls -al libc-2.0.7.so
-rwxr-xr-x 1 root root 647572 Nov 27 04:23 libc-2.0.7.so
[root@localhost /lib]# ldd `which ls`
libc.so.6 => /lib/libc.so.6 (0x40006000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)
[root@localhost /lib]# ls -al libc.so.6
lrwxrwxrwx 1 root root 13 May 31 06:50 libc.so.6 -> libc-2.0.7.so
[root@localhost /lib]#
-- cut --
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/