From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the xen tree
Date: Thu, 22 Jul 2010 23:05:10 -0700 [thread overview]
Message-ID: <4C493116.1040107@goop.org> (raw)
In-Reply-To: <20100723140107.2883b2d3.sfr@canb.auug.org.au>
On 07/22/2010 09:01 PM, Stephen Rothwell wrote:
> arch/x86/xen/enlighten.c:71: error: __pcpu_scope_xen_vcpu causes a section type conflict
> arch/x86/xen/enlighten.c:72: error: __pcpu_scope_xen_vcpu_info causes a section type conflict
> arch/x86/xen/enlighten.c:71: error: __pcpu_unique_xen_vcpu causes a section type conflict
> arch/x86/xen/enlighten.c:72: error: __pcpu_unique_xen_vcpu_info causes a section type conflict
> arch/x86/xen/enlighten.c:558: error: __pcpu_unique_idt_desc causes a section type conflict
> arch/x86/xen/enlighten.c:760: error: __pcpu_unique_xen_cr0_value causes a section type conflict
>
> Not sure what has caused this. I have dropped the xen tree for today.
>
> gcc version 4.4.4 binutils version 2.20.1.
>
I've updated upstream/xen with the patch I just posted to fix this problem.
Thanks,
J
next prev parent reply other threads:[~2010-07-23 6:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 4:01 linux-next: build failure after merge of the xen tree Stephen Rothwell
2010-07-23 4:48 ` Jeremy Fitzhardinge
2010-07-23 5:56 ` Jeremy Fitzhardinge
2010-07-23 6:05 ` Jeremy Fitzhardinge [this message]
2010-07-23 6:59 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-07-28 4:18 Stephen Rothwell
2010-10-25 2:30 Stephen Rothwell
2010-10-25 8:38 ` Ian Campbell
2010-10-25 8:38 ` Ian Campbell
2010-10-25 23:57 ` Jeremy Fitzhardinge
2010-10-27 2:02 Stephen Rothwell
2011-09-15 5:27 Stephen Rothwell
2011-09-15 9:10 ` Jeremy Fitzhardinge
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=4C493116.1040107@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.