From: Adrian Bunk <bunk@fs.tum.de>
To: Eric BEGOT <eric_begot@yahoo.fr>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.27-pre5
Date: Sun, 6 Jun 2004 14:15:46 +0200 [thread overview]
Message-ID: <20040606121545.GB5830@fs.tum.de> (raw)
In-Reply-To: <40C19EDE.10405@yahoo.fr>
> >On Fri, Jun 04, 2004 at 04:41:17PM +0200, Eric BEGOT wrote:
> >
> >
> >>when compiling linux-2.4.27-pre5 under a x86 architecture, I've a lot of
> >>warnings :
> >>
> >>In file included from
> >>/usr/src/devel//usr/src/devel/include/linux/modules/i386_ksyms.ver:127:1:
> >>warning: "__ver_atomic_dec_and_lock" redefined
> >>In file included from /usr/src/devel/include/linux/modversions.h:70,
> >> from <command line>:8:
> >>/usr/src/devel/include/linux/modules/dec_and_lock.ver:1:1: warning: this
> >>is the location of the previous definition
> >>
> >>__ver_atomic_dec_and_lock is declared two times. Maybe it lacks a #ifdef
> >>somewhere in the modversions.h no ?
> >>The compilation doesn't fail bu it's not very nice :)
I can't reproduce your problem with your .config .
Did you do something like patching the kernel or changing the SMP option
without running "make oldconfig" afterwards?
What are the values of __ver_atomic_dec_and_lock at the two places
mentiones in the warnings?
Does a
cp .config /tmp
make mrproper
mv /tmp/.config
make oldconfig
make bzImage
fix this problem?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-06-06 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 2:24 Linux 2.4.27-pre5 Marcelo Tosatti
2004-06-03 13:31 ` Andreas Haumer
2004-06-04 8:38 ` Matthias Andree
2004-06-04 12:46 ` Marcelo Tosatti
2004-06-04 14:41 ` Eric BEGOT
2004-06-04 22:52 ` Adrian Bunk
2004-06-05 10:22 ` Eric BEGOT
2004-06-06 12:15 ` Adrian Bunk [this message]
2004-06-06 18:11 ` Eric BEGOT
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=20040606121545.GB5830@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=eric_begot@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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