From: dth@ncc1701.cistron.net (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.20-rc1-ac2
Date: Thu, 14 Nov 2002 16:44:22 +0000 (UTC) [thread overview]
Message-ID: <ar0jt6$fas$1@ncc1701.cistron.net> (raw)
In-Reply-To: 200211141622.gAEGMhX17361@devserv.devel.redhat.com
Alan Cox <alan@redhat.com> wrote:
>Linux 2.4.20-rc1-ac2
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-rc1-ac2/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i586 -nostdinc -iwithprefix include -DKBUILD_BASENAME=rmap -c -o rmap.o rmap.c
In file included from rmap.c:31:
/usr/src/linux-2.4.20-rc1-ac2/include/asm/smplock.h:17: warning: `kernel_locked' redefined
/usr/src/linux-2.4.20-rc1-ac2/include/linux/smp_lock.h:12: warning: this is the location of the previous definition
/usr/src/linux-2.4.20-rc1-ac2/include/asm/smplock.h:28: warning: `release_kernel_lock' redefined
/usr/src/linux-2.4.20-rc1-ac2/include/linux/smp_lock.h:10: warning: this is the location of the previous definition
/usr/src/linux-2.4.20-rc1-ac2/include/asm/smplock.h:37: warning: `reacquire_kernel_lock' redefined
/usr/src/linux-2.4.20-rc1-ac2/include/linux/smp_lock.h:11: warning: this is the location of the previous definition
/usr/src/linux-2.4.20-rc1-ac2/include/asm/smplock.h:47: arguments given to macro `lock_kernel'
/usr/src/linux-2.4.20-rc1-ac2/include/asm/smplock.h:63: arguments given to macro `unlock_kernel'
In file included from rmap.c:31:
/usr/src/linux-2.4.20-rc1-ac2/include/asm/smplock.h:47: parse error before `do'
/usr/src/linux-2.4.20-rc1-ac2/include/asm/smplock.h:63: parse error before `do'
make[3]: *** [rmap.o] Error 1
next prev parent reply other threads:[~2002-11-14 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 16:22 Linux 2.4.20-rc1-ac2 Alan Cox
2002-11-14 16:44 ` Danny ter Haar [this message]
2002-11-14 19:13 ` David Dyck
2002-11-14 17:31 ` Tom Rini
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='ar0jt6$fas$1@ncc1701.cistron.net' \
--to=dth@ncc1701.cistron.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