From: Andi Kleen <ak@suse.de>
To: Voluspa <lista1@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.16-gitX] (x86_64) WARNING: vmlinux: 'strlen' exported twice. Previous export was in vmlinux
Date: Thu, 30 Mar 2006 04:05:58 +0200 [thread overview]
Message-ID: <200603300405.59138.ak@suse.de> (raw)
In-Reply-To: <20060330035318.41a5b74c.lista1@telia.com>
On Thursday 30 March 2006 03:53, Voluspa wrote:
>
> Git versions keep incrementing but no fix for:
>
> BUILD arch/x86_64/boot/bzImage
> Root device is (3, 2)
> Boot sector 512 bytes.
> Setup is 4696 bytes.
> System is 1530 kB
> Kernel: arch/x86_64/boot/bzImage is ready (#1)
> Building modules, stage 2.
> MODPOST
> WARNING: vmlinux: 'strlen' exported twice. Previous export was in vmlinux
>
> And every module built ouside of the kernel also spews that message. Has
> been the case since this got in:
My kernel build doesn't say that. Please send your .config and state
which gcc version are you using.
-Andi
next prev parent reply other threads:[~2006-03-30 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 1:53 [2.6.16-gitX] (x86_64) WARNING: vmlinux: 'strlen' exported twice. Previous export was in vmlinux Voluspa
2006-03-30 2:05 ` Andi Kleen [this message]
2006-03-30 2:17 ` Voluspa
2006-03-30 10:31 ` Andi Kleen
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=200603300405.59138.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@telia.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