I get some warnings about unused names (actually static arrays of 256
bytes each) in the nls_cp???.c files when I compile 2.0.36 (with
wanpipe 2.0.4 patch, but it doesn't touch these files).
Here is the relevant section:
gcc -D__KERNEL__ -I/usr/src/linux-2.0.36+wanpipe-2.0.4/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -D__SMP__ -pipe -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -D__SMP__ -c -o nls_cp862.o nls_cp862.c
nls_cp437.c:361: warning: `charset2upper' defined but not used
gcc -D__KERNEL__ -I/usr/src/linux-2.0.36+wanpipe-2.0.4/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -D__SMP__ -pipe -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -D__SMP__ -c -o nls_iso8859_1.o nls_iso8859_1.c
nls_cp862.c:397: warning: `charset2upper' defined but not used
gcc -D__KERNEL__ -I/usr/src/linux-2.0.36+wanpipe-2.0.4/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -D__SMP__ -pipe -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -D__SMP__ -c -o nls_iso8859_8.o nls_iso8859_8.c
nls_iso8859_1.c:138: warning: `charset2upper' defined but not used
gcc -D__KERNEL__ -I/usr/src/linux-2.0.36+wanpipe-2.0.4/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -D__SMP__ -pipe -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -D__SMP__ -c -o open.o open.c
nls_iso8859_8.c:214: warning: `charset2upper' defined but not used
I added only the US and Hebrew support files, so this might be
relevant in other nls files as well.
Please CC replys to me, as I'm not on the linux-kernel mailing list.
Thanks.
--Amos
--Amos Shapira | "Of course Australia was marked for
133 Shlomo Ben-Yosef st. | glory, for its people had been chosen
Jerusalem 93 805 | by the finest judges in England."
ISRAEL amos@gezernet.co.il | -- Anonymous
-
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/