From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Michael Guntsche <mike@it-loops.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Compile error with 2.6.34-rc5+
Date: Thu, 22 Apr 2010 16:27:21 +0200 [thread overview]
Message-ID: <201004221627.23600.s.L-H@gmx.de> (raw)
In-Reply-To: <20100422134550.GA4886@gibson.comsick.at>
Hi
On Thursday 22 April 2010, Michael Guntsche wrote:
> Hi,
>
> While compiling current git HEAD on one of my boxes I got a compile error.
> Current head is at 1ef6ce7a340f9ed139a73147ff9cf7ad56889414 and the
> compile error is
>
> drivers/built-in.o: In function `raid5_compute_sector':
> raid5.c:(.text+0x85a36): undefined reference to `__umoddi3'
> raid5.c:(.text+0x85a67): undefined reference to `__umoddi3'
> raid5.c:(.text+0x85a9c): undefined reference to `__umoddi3'
> raid5.c:(.text+0x85acd): undefined reference to `__umoddi3'
> raid5.c:(.text+0x85b23): undefined reference to `__umoddi3'
> drivers/built-in.o:raid5.c:(.text+0x85b54): more undefined references to
> `__umoddi3' follow
This seems to be the same problem as
http://lkml.indiana.edu/hypermail/linux/kernel/1004.2/01814.html
fixed in
http://lkml.indiana.edu/hypermail/linux/kernel/1004.2/01816.html
> The config file was taken straight from a -rc4 kernel and make oldconfig
> was run before that.
> This runs on/is compiled for a 32bit Pentium IV system so I wonder why umoddi3 is being used.
>
> Kind regards,
> Michael
Regards
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2010-04-22 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:45 Compile error with 2.6.34-rc5+ Michael Guntsche
2010-04-22 14:27 ` Stefan Lippers-Hollmann [this message]
2010-04-22 16:16 ` Michael Guntsche
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=201004221627.23600.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mike@it-loops.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;
as well as URLs for NNTP newsgroup(s).