All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Neil Brown <neilb@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: tip: origin tree build failure (x86, 32-bit, allyesconfig)
Date: Thu, 22 Apr 2010 09:06:10 +0200	[thread overview]
Message-ID: <20100422070610.GA18884@elte.hu> (raw)
In-Reply-To: <19350.53522.385933.467438@notabene.brown>


* Neil Brown <neilb@suse.de> wrote:

> are available in the git repository at:
> 
>   git://neil.brown.name/md/ for-linus

( Note, i'm re-using this old MD pull request thread to report a bug in a pull 
  request you sent to Linus in the past two days. I havent found the pull 
  request nor the patch on lkml. )

All 32-bit x86 builds (x86, allyesconfig) that enable RAID are failing with 
this build failure:

 drivers/built-in.o: In function `raid5_compute_sector':
 raid5.c:(.text+0x2e42ac): undefined reference to `__umoddi3'
 raid5.c:(.text+0x2e42d8): undefined reference to `__umoddi3'
 raid5.c:(.text+0x2e42ff): undefined reference to `__umoddi3'
 raid5.c:(.text+0x2e4327): undefined reference to `__umoddi3'
 raid5.c:(.text+0x2e4385): undefined reference to `__umoddi3'
 drivers/built-in.o:raid5.c:(.text+0x2e43bc): more undefined references to `__umoddi3' follow

Caused by this commit:

  35f2a59: md/raid5: allow for more than 2^31 chunks.

I've reverted the commit from -tip for now.

Thanks,

	Ingo

  reply	other threads:[~2010-04-22  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 22:52 [PULL REQUEST] minor md updates for 2.6.34 Neil Brown
2010-04-22  7:06 ` Ingo Molnar [this message]
2010-04-22 18:12   ` tip: origin tree build failure (x86, 32-bit, allyesconfig) Linus Torvalds
2010-04-22 21:13     ` Neil Brown

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=20100422070610.GA18884@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=torvalds@linux-foundation.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.