From: Borislav Petkov <bp@alien8.de>
To: "Michael D. Setzer II" <msetzerii@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Error in linux-3.0.72 build.
Date: Sat, 6 Apr 2013 13:26:57 +0200 [thread overview]
Message-ID: <20130406112657.GA3625@pd.tnic> (raw)
In-Reply-To: <515FF835.28644.1FF1E@msetzerii.gmail.com>
On Sat, Apr 06, 2013 at 08:25:57PM +1000, Michael D. Setzer II wrote:
> Just downloaded new kernels, and find this error in build.
>
> fs/built-in.o: In function `find_group_flex':
> /home/msetzerii/data/linux-3.0.72/fs/ext4/ialloc.c:359: undefined
> reference to `__udivdi3'
> /home/msetzerii/data/linux-3.0.72/fs/ext4/ialloc.c:374: undefined
> reference to `__udivdi3'
> make: *** [.tmp_vmlinux1] Error 1
Looks like your compiler is generating 64-bit division which is a call
into libgcc. Which gcc version are you using?
+ext4 folks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next parent reply other threads:[~2013-04-06 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <515FF835.28644.1FF1E@msetzerii.gmail.com>
2013-04-06 11:26 ` Borislav Petkov [this message]
2013-04-06 11:32 ` Error in linux-3.0.72 build Michael D. Setzer II
2013-04-06 12:02 ` Michael D. Setzer II
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=20130406112657.GA3625@pd.tnic \
--to=bp@alien8.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msetzerii@gmail.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).