From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jeremy Fitzhardinge <jeremy@goop•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build failure after merge of the xen tree
Date: Fri, 23 Jul 2010 14:01:07 +1000 [thread overview]
Message-ID: <20100723140107.2883b2d3.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
Hi Jeremy,
After merging the xen tree, today's linux-next build (86_64 allmodconfig)
failed like this:
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.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2010-07-23 4:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 4:01 Stephen Rothwell [this message]
2010-07-23 4:48 ` linux-next: build failure after merge of the xen tree Jeremy Fitzhardinge
2010-07-23 5:56 ` Jeremy Fitzhardinge
2010-07-23 6:05 ` Jeremy Fitzhardinge
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 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=20100723140107.2883b2d3.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jeremy@goop$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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