From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [stable-2.6.31/master] Compile error "error: redefinition of xen_destroy_irq"
Date: Mon, 15 Mar 2010 21:50:32 -0400 [thread overview]
Message-ID: <20100316015032.GA24571@phenom.dumpdata.com> (raw)
In-Reply-To: <797005095.20100311095154@eikelenboom.it>
On Thu, Mar 11, 2010 at 09:51:54AM +0100, Sander Eikelenboom wrote:
> Hello Konrad,
>
> You patch results in another compile error, it seems these are all caused by NOT enabling dom0 support in the kernel (i was building a kernel for a domU, so I thought I don't need it, just leave it out)
>
> Hello Konrad,
>
> Hmm that seems to give another one:
>
> AS arch/x86/lib/thunk_64.o
> CC arch/x86/lib/usercopy_64.o
> AR arch/x86/lib/lib.a
> LD vmlinux.o
> MODPOST vmlinux.o
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `pcifront_init':
> xen-pcifront.c:(.init.text+0x257b): undefined reference to `xen_pci_frontend'
> drivers/built-in.o: In function `pcifront_cleanup':
> xen-pcifront.c:(.exit.text+0xa8): undefined reference to `xen_pci_frontend'
> make: *** [.tmp_vmlinux1] Error 1
Ugh. Let me spin out another patch to address this fallout.
next prev parent reply other threads:[~2010-03-16 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 18:42 [stable-2.6.31/master] Compile error "error: redefinition of xen_destroy_irq" Sander Eikelenboom
2010-03-10 19:54 ` Konrad Rzeszutek Wilk
2010-03-10 22:19 ` Sander Eikelenboom
2010-03-11 8:51 ` Sander Eikelenboom
2010-03-16 1:50 ` Konrad Rzeszutek Wilk [this message]
2010-03-16 19:58 ` Konrad Rzeszutek Wilk
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=20100316015032.GA24571@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.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 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.