From: Frank Jacobberger <f1j@xmission.com>
To: linux-kernel@vger.kernel.org
Subject: lcalls ???
Date: Tue, 05 Dec 2000 07:38:34 -0700 [thread overview]
Message-ID: <3A2CFDEA.C2E61BE6@xmission.com> (raw)
Would someone be so kind and inform where I might go ferret out why I'm
getting these multiple lcalls from pci-pc.o?
Would I look real hard at General Setup in make menuconfig??
The kernels I have maked all work, but this little area puzzles me....
_______________________________________________________________________
kgcc -D_KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -c -o
pci-pc.o pci-pc.c
{standard input}: Assembler messages:
{standard input} 829: Warning: indirect lcall without `*'
{standard input}:911: Warning: indirect lcall without `*'
{standard input}:1006: Warning: indirect lcall without `*'
{standard input}:1046: Warning: indirect lcall without `*'
{standard input}:1076: Warning: indirect lcall without `*'
{standard input}:1106: Warning: indirect lcall without `*'
{standard input}:1137: Warning: indirect lcall without `*'
{standard input}:1166: Warning: indirect lcall without `*'
{standard input}:1195: Warning: indirect lcall without `*'
{standard input}:1497: Warning: indirect lcall without `*'
{standard input}:1592: Warning: indirect lcall without `*'
kgcc -D_KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -c -o
pci-irq.o pci-irq.c
________________________________________________________________________
Any pointers here would be appreciated.
Thanks again,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-05 15:09 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=3A2CFDEA.C2E61BE6@xmission.com \
--to=f1j@xmission.com \
--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