From: Sven Vermeulen <sven.vermeulen@rug.ac.be>
To: Linux-Kernel Development Mailinglist <linux-kernel@vger.kernel.org>
Subject: 2.4.14-pre3: some compilerwarnings...
Date: Sat, 27 Oct 2001 18:51:58 +0200 [thread overview]
Message-ID: <20011027185158.A5848@Zenith.starcenter> (raw)
A little grep on the stdout/stderr of "make bzImage":
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o fork.o fork.c
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o exec_domain.o exec_domain.c
exec_domain.c: In function `lookup_exec_domain':
exec_domain.c:80: warning: unused variable `buffer'
--
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o misc.o misc.c
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o random.o random.c
random.c: In function `xfer_secondary_pool':
random.c:1248: warning: comparison of distinct pointer types lacks a cast
--
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o procfs.o procfs.c
ld -m elf_i386 -r -o parport.o share.o ieee1284.o ieee1284_ops.o init.o procfs.o
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o parport_pc.o parport_pc.c
parport_pc.c:94: warning: `verbose_probing' defined but not used
parport_pc.c:2007: warning: `parport_ECP_supported' defined but not used
--
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o buffer.o buffer.c
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o super.o super.c
super.c: In function `mount_root':
super.c:1064: warning: label `attach_it' defined but not used
--
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o i387.o i387.c
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o bluesmoke.o bluesmoke.c
gcc -D__KERNEL__ -I/home/nitro/src/linux-2.4.13/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o dmi_scan.o dmi_scan.c
dmi_scan.c:194: warning: `disable_ide_dma' defined but not used
--
I have no problems believing that some (most) of them are due to my .config,
but, as I said before, I *hate* warnings :)
--
You might as well skip the Xmas celebration completely, and instead
sit in front of your Linux computer playing with the
all-new-and-improved Linux kernel version. ~(Linus Torvalds)
next reply other threads:[~2001-10-27 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-27 16:51 Sven Vermeulen [this message]
2001-10-27 17:16 ` 2.4.14-pre3: some compilerwarnings Robert Love
2001-10-27 17:30 ` [PATCH] " Robert Love
2001-10-31 17:12 ` Ragnar Hojland Espinosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011027185158.A5848@Zenith.starcenter \
--to=sven.vermeulen@rug.ac.be \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox