From: majianpeng <majianpeng@gmail.com>
To: tglx <tglx@linutronix.de>
Cc: x86 <x86@kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: compile x86_64 waring
Date: Fri, 5 Jul 2013 19:56:07 +0800 [thread overview]
Message-ID: <201307051956052638321@gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 983 bytes --]
Hi all,
Compile x86_64 meet those messages:
WARNING: arch/x86/mm/built-in.o(.text.unlikely+0xbf8): Section mismatch in reference from the function __node_set.constprop.0() to the variable .init.data:numa_nodes_parsed
The function __node_set.constprop.0() references
the variable __initdata numa_nodes_parsed.
This is often because __node_set.constprop.0 lacks a __initdata
annotation or the annotation of numa_nodes_parsed is wrong.
WARNING: arch/x86/built-in.o(.text.unlikely+0x171d): Section mismatch in reference from the function __node_set.constprop.0() to the variable .init.data:numa_nodes_parsed
The function __node_set.constprop.0() references
the variable __initdata numa_nodes_parsed.
This is often because __node_set.constprop.0 lacks a __initdata
annotation or the annotation of numa_nodes_parsed is wrong.ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2013-07-05 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 11:56 majianpeng [this message]
2013-07-24 21:05 ` compile x86_64 waring Paul Bolle
2013-07-24 23:22 ` Tom Rini
2013-07-25 8:53 ` Paul Bolle
2013-07-25 9:41 ` Paul Bolle
2013-07-25 12:17 ` Tom Rini
2013-10-30 13:04 ` Leon Gorge
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=201307051956052638321@gmail.com \
--to=majianpeng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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.