From: Kristian Peters <kristian.peters@korseby.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.10 - Warning: indirect lcall without `*'
Date: Tue, 25 Sep 2001 22:34:14 +0200 [thread overview]
Message-ID: <3BB0EA46.1070001@korseby.net> (raw)
Shouldn't that fixed earlier ?
I use gcc 2.95.3.
make[1]: Entering directory `/usr/src/linux-2.4.10/arch/i386/boot'
gcc -E -D__KERNEL__ -I/usr/src/linux-2.4.10/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:257: Warning: indirect lcall without `*'
ld -m elf_i386 -Ttext 0x0 -s --oformat binary bbootsect.o -o bbootsect
gcc -E -D__KERNEL__ -I/usr/src/linux-2.4.10/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:1912: Warning: indirect lcall without `*'
reply other threads:[~2001-09-25 20:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BB0EA46.1070001@korseby.net \
--to=kristian.peters@korseby.net \
--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
all inboxes | Powered by JetHome®