From: Rudmer van Dijk <rudmer@legolas.dynup.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-rc4
Date: Thu, 1 Aug 2002 07:40:39 +0200 [thread overview]
Message-ID: <20020801053133Z318627-685+21899@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0207311819060.1026-100000@freak.distro.conectiva>
On Wednesday 31 July 2002 23:20, Marcelo Tosatti wrote:
> Hi,
>
> Since some critical problems appeared (mainly the d_unhash() SMP race)
> here is rc4.
>
Found these warnings when compiling:
gcc -D__KERNEL__ -I/home/rudmer/src/kernel/linux-2.4.19-rc4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-malign-functions=4 -nostdinc -I
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/include -DKBUILD_BASENAME=setup -c
-o setup.o setup.c
setup.c: In function `amd_adv_spec_cache_feature':
setup.c:751: warning: implicit declaration of function `have_cpuid_p'
setup.c: At top level:
setup.c:2629: warning: `have_cpuid_p' was declared implicitly `extern' and
later `static'
setup.c:751: warning: previous declaration of `have_cpuid_p'
<snip>
gcc -D__KERNEL__ -I/home/rudmer/src/kernel/linux-2.4.19-rc4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-malign-functions=4 -nostdinc -I
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/include -DKBUILD_BASENAME=pci_pc
-c -o pci-pc.o pci-pc.c
{standard input}: Assembler messages:
{standard input}:1066: Warning: indirect lcall without `*'
{standard input}:1151: Warning: indirect lcall without `*'
{standard input}:1238: Warning: indirect lcall without `*'
{standard input}:1311: Warning: indirect lcall without `*'
{standard input}:1322: Warning: indirect lcall without `*'
{standard input}:1333: Warning: indirect lcall without `*'
{standard input}:1410: Warning: indirect lcall without `*'
{standard input}:1422: Warning: indirect lcall without `*'
{standard input}:1434: Warning: indirect lcall without `*'
{standard input}:1914: Warning: indirect lcall without `*'
{standard input}:2019: Warning: indirect lcall without `*'
<snip>
gcc -D__KERNEL__ -I/home/rudmer/src/kernel/linux-2.4.19-rc4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-malign-functions=4 -nostdinc -I
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/include -DKBUILD_BASENAME=apm -c
-o apm.o apm.c
{standard input}: Assembler messages:
{standard input}:237: Warning: indirect lcall without `*'
{standard input}:331: Warning: indirect lcall without `*'
output from scripts/ver_linux:
Linux gandalf 2.4.19-rc3-ac4 #2 Wed Jul 31 21:23:51 CEST 2002 i686 unknown
Gnu C 2.95.3
Gnu make 3.79.1
util-linux 2.11q
mount 2.11q
modutils 2.4.16
e2fsprogs 1.27
Linux C Library 2.2.5
Dynamic linker (ldd) 2.2.5
Procps 2.0.7
Net-tools 1.60
Kbd 1.06
Sh-utils 2.0
my binutils is 2.12 and the script does not mention it... if I change the
scripts binutils 'detection' to:
ld -v 2>&1 | awk 'NR==1 {print "binutils ",$4}'
then it gets listed.
Rudmer
prev parent reply other threads:[~2002-08-01 5:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 21:20 Marcelo Tosatti
2002-08-01 5:40 ` Rudmer van Dijk [this message]
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=20020801053133Z318627-685+21899@vger.kernel.org \
--to=rudmer@legolas.dynup.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®