From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Parag Warudkar <parag.warudkar@gmail.com>,
linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
Zachary Amsden <zach@vmware.com>
Subject: Re: 07/26 GIT - Build breakage
Date: Fri, 27 Jul 2007 10:59:24 +1000 [thread overview]
Message-ID: <1185497965.12151.2.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.0.999.0707261605560.3442@woody.linux-foundation.org>
On Thu, 2007-07-26 at 16:07 -0700, Linus Torvalds wrote:
>
> On Thu, 26 Jul 2007, Parag Warudkar wrote:
> >
> > arch/i386/kernel/paravirt.o: In function `init_IRQ':
> > (.text+0xb20): multiple definition of `init_IRQ'
> > arch/i386/kernel/i8259.o:(.init.text+0x30): first defined here
> > ld: Warning: size of symbol `init_IRQ' changed from 66 in
> > arch/i386/kernel/i8259.o to 14 in arch/i386/kernel/paravirt.o
> > make[1]: *** [arch/i386/kernel/built-in.o] Error 1
> > make: *** [arch/i386/kernel] Error 2
>
> Ok, it seems that some versions of gcc/binutils have problems with the
> games that paravirt introduced with the "weak" thing.
>
> I'm not entirely surprised. That stuff was trying to be too clever by
> half.
>
> Rusty?
Sure, but this was in .21 and .22. This config is from 2.6.21.5, in
fact.
Parag, does your arch/i386/kernel/i8259.c look like this around line
384? If not, perhaps it's a mis-merge for you?
/* Overridden in paravirt.c */
void init_IRQ(void) __attribute__((weak, alias("native_init_IRQ")));
void __init native_init_IRQ(void)
{
Thanks,
Rusty.
next prev parent reply other threads:[~2007-07-27 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 22:48 07/26 GIT - Build breakage Parag Warudkar
2007-07-26 23:07 ` Linus Torvalds
2007-07-27 0:59 ` Rusty Russell [this message]
2007-07-27 1:09 ` Parag Warudkar
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=1185497965.12151.2.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox