From: Rusty Lynch <rusty@linux.co.intel.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.63-bk6 compile error] __crc_page_states__per_cpu not in per-cpu section
Date: 03 Mar 2003 11:13:24 -0800 [thread overview]
Message-ID: <1046718805.2819.19.camel@vmhack> (raw)
In-Reply-To: <Pine.LNX.4.44.0303031306390.16397-100000@chaos.physics.uiowa.edu>
yes, this works for me.
--rustyl
On Mon, 2003-03-03 at 11:10, Kai Germaschewski wrote:
> On 3 Mar 2003, Rusty Lynch wrote:
>
> > After updating my bk tree this morning, I am getting the
> > following compile error:
> >
> > 4d13d7e9 A __crc_page_states__per_cpu not in per-cpu section
> > make: *** [vmlinux] Error 1
>
> It's a false positive from the script which checks whether all per-cpu
> variables ended up in the correct section. __crc_page_states__per_cpu ends
> in __per_cpu, that's why the script thinks it's a per-cpu variable, but
> it's not, it's just a checksum.
>
> Could you try if this patch fixes it, I don't really speak awk ;)
>
> You should be able to reproduce the error by just doing "rm vmlinux; make
> vmlinux", but not anymore after applying the patch below.
>
> --Kai
>
>
> ===== scripts/per-cpu-check.awk 1.3 vs edited =====
> --- 1.3/scripts/per-cpu-check.awk Fri Jan 24 14:27:01 2003
> +++ edited/scripts/per-cpu-check.awk Mon Mar 3 13:05:48 2003
> @@ -6,7 +6,7 @@
> IN_PER_CPU=0
> }
>
> -/__per_cpu$$/ && ! ( / __ksymtab_/ || / __kstrtab_/ || / __kcrctab_/ ) {
> +/__per_cpu$$/ && ! ( / __ksymtab_/ || / __kstrtab_/ || / __kcrctab_/ || / __crc_/ ) {
> if (!IN_PER_CPU) {
> print $$3 " not in per-cpu section" > "/dev/stderr";
> FOUND=1;
>
prev parent reply other threads:[~2003-03-03 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 17:38 [2.5.63-bk6 compile error] __crc_page_states__per_cpu not in per-cpu section Rusty Lynch
2003-03-03 19:10 ` Kai Germaschewski
2003-03-03 19:13 ` Rusty Lynch [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=1046718805.2819.19.camel@vmhack \
--to=rusty@linux.co.intel.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.