From: Sven Vermeulen <sven.vermeulen@rug.ac.be>
To: Linux-Kernel Development Mailinglist <linux-kernel@vger.kernel.org>
Subject: 2.4.13: some compilerwarnings...
Date: Wed, 24 Oct 2001 19:53:42 +0200 [thread overview]
Message-ID: <20011024195342.A464@Zenith.starcenter> (raw)
No fatal errors or anything, kernel runs fine, but some compilerwarnings...
they could be in other kernelversions too, I only noticed them this time.
~$ make dep
[...]
make -C eicon fastdep
make[6]: Entering directory `/home/nitro/src/linux/drivers/isdn/eicon'
/home/nitro/src/linux/scripts/mkdep -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -- Divas_mod.c adapter.h bri.c common.c constant.h divalog.h divas.h dsp_defs.h dspdids.h eicon.h eicon_dsp.h eicon_idi.c eicon_idi.h eicon_io.c eicon_isa.c eicon_isa.h eicon_mod.c eicon_pci.c eicon_pci.h fourbri.c fpga.c idi.c idi.h kprintf.c lincfg.c linchr.c linio.c linsys.c log.c pc.h pc_maint.h pr_pc.h pri.c sys.h uxio.h xlog.c > .depend
make[6]: Leaving directory `/home/nitro/src/linux/drivers/isdn/eicon'
make -C hisax fastdep
md5sum: WARNING: 13 of 13 computed checksums did NOT match
[...]
~$ make bzImage
[...]
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o pci-i386.o pci-i386.c
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o pci-pc.o pci-pc.c
{standard input}: Assembler messages:
{standard input}:1040: Warning: indirect lcall without `*'
{standard input}:1125: Warning: indirect lcall without `*'
{standard input}:1208: Warning: indirect lcall without `*'
{standard input}:1282: Warning: indirect lcall without `*'
{standard input}:1293: Warning: indirect lcall without `*'
{standard input}:1304: Warning: indirect lcall without `*'
{standard input}:1378: Warning: indirect lcall without `*'
{standard input}:1389: Warning: indirect lcall without `*'
{standard input}:1400: Warning: indirect lcall without `*'
{standard input}:1862: Warning: indirect lcall without `*'
{standard input}:1951: Warning: indirect lcall without `*'
[...]
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o msr.o msr.c
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o apm.o apm.c
{standard input}: Assembler messages:
{standard input}:187: Warning: indirect lcall without `*'
{standard input}:282: Warning: indirect lcall without `*'
[...]
gcc -E -D__KERNEL__ -I/home/nitro/src/linux/include -D__BIG_KERNEL__ -traditional -DSVGA_MODE=NORMAL_VGA bootsect.S -o bbootsect.s
as -o bbootsect.o bbootsect.s
bbootsect.s: Assembler messages:
bbootsect.s:256: Warning: indirect lcall without `*'
[...]
gcc -E -D__KERNEL__ -I/home/nitro/src/linux/include -D__BIG_KERNEL__ -D__ASSEMBLY__ -traditional -DSVGA_MODE=NORMAL_VGA setup.S -o bsetup.s
as -o bsetup.o bsetup.s
bsetup.s: Assembler messages:
bsetup.s:1459: Warning: indirect lcall without `*'
[...]
btw: gcc-version is 2.96, as-version is 2.11.90.0.8
Keep up the good work!
Sven Vermeulen
--
Unix, MS-DOS and Windows NT (also known as the Good, the Bad and the
Ugly). ~(Matt Welsh)
next reply other threads:[~2001-10-24 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 17:53 Sven Vermeulen [this message]
2001-10-24 18:07 ` 2.4.13: some compilerwarnings Dave Jones
2001-10-24 18:25 ` Sven Vermeulen
2001-10-24 18:48 ` Dave Jones
2001-10-25 18:15 ` André Dahlqvist
2001-10-24 22:20 ` Alan Cox
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=20011024195342.A464@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.