From: David Balazic <david.balazic@uni-mb.si>
To: alan@lxorguk.ukuu.org.uk
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.4-ac10
Date: Fri, 18 May 2001 10:12:27 +0200 [thread overview]
Message-ID: <3B04D96B.FCDA69E9@uni-mb.si> (raw)
Alan Cox (alan@lxorguk.ukuu.org.uk) wrote :
> >
> > gcc -D__KERNEL__ -I/usr/src/linux-2.4.4-ac/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
> -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -c -o apm.o apm.c
> > {standard input}: Assembler messages:
> > {standard input}:180: Warning: indirect lcall without `*'
> > {standard input}:274: Warning: indirect lcall without `*'
> >
> > Does anyone know what's up with that? Kernel problem or binutils issue?
>
> binutils is issuing a correct warning but if we fix the warning old old binutils
> will then refuse to assemble it right.
What old old binutils ?
Isn't there a clear requirement for a minimum binutils version in
Documentation/Changes ( or maybe it is README ... ) ?
--
David Balazic
--------------
"Be excellent to each other." - Bill & Ted
- - - - - - - - - - - - - - - - - - - - - -
next reply other threads:[~2001-05-18 8:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 8:12 David Balazic [this message]
2001-05-18 8:51 ` Linux 2.4.4-ac10 André Dahlqvist
-- strict thread matches above, loose matches on Subject: below --
2001-05-17 16:45 Alan Cox
2001-05-17 17:00 ` Christoph Hellwig
2001-05-17 17:36 ` Alan Cox
2001-05-17 17:16 ` Chris Evans
2001-05-17 17:37 ` Rik van Riel
2001-05-17 17:47 ` Mike Galbraith
2001-05-17 21:03 ` Rik van Riel
2001-05-18 3:55 ` Sasi Peter
2001-05-18 4:03 ` Rik van Riel
2001-05-18 6:06 ` Mike Galbraith
2001-05-18 17:08 ` Rik van Riel
2001-05-18 17:45 ` Mike Galbraith
2001-05-18 18:19 ` Ingo Oeser
2001-05-18 18:23 ` Rik van Riel
2001-05-18 18:58 ` Ingo Oeser
2001-05-18 20:12 ` Rik van Riel
2001-05-18 20:24 ` Mike Galbraith
2001-05-18 20:09 ` Mike Galbraith
2001-05-18 22:44 ` Rik van Riel
2001-05-18 22:58 ` Stephen C. Tweedie
2001-05-19 2:12 ` Rik van Riel
2001-05-19 2:32 ` Mike Castle
2001-05-19 6:45 ` Mike Galbraith
2001-05-19 4:40 ` Mike Galbraith
2001-05-17 17:26 ` Geert Uytterhoeven
2001-05-17 18:33 ` Udo A. Steinberg
2001-05-17 18:40 ` Matti Aarnio
2001-05-17 18:51 ` Matti Aarnio
2001-05-17 19:21 ` Alan Cox
2001-05-17 18:46 ` Ingo Oeser
2001-05-17 19:00 ` J . A . Magallon
2001-05-17 19:05 ` Jeff Garzik
2001-05-17 19:26 ` 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=3B04D96B.FCDA69E9@uni-mb.si \
--to=david.balazic@uni-mb.si \
--cc=alan@lxorguk.ukuu.org.uk \
--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