From: Mikulas Patocka <mpatocka@redhat•com>
To: Adrian Bunk <bunk@kernel•org>
Cc: Thomas Meyer <thomas@m3y3r•de>,
Linux Kernel <linux-kernel@vger•kernel.org>,
linux-next@vger•kernel.org
Subject: Re: next-20080723: build fails for dm-snapshot.ko
Date: Wed, 23 Jul 2008 14:33:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0807231431250.3332@devserv.devel.redhat.com> (raw)
In-Reply-To: <20080723182839.GF14846@cs181140183.pp.htv.fi>
On Wed, 23 Jul 2008, Adrian Bunk wrote:
> On Wed, Jul 23, 2008 at 07:58:37PM +0200, Thomas Meyer wrote:
> >
> > Building modules, stage 2.
> > Kernel: arch/x86/boot/bzImage is ready (#24)
> > MODPOST 1518 modules
> > ERROR: "__umoddi3" [drivers/md/dm-snapshot.ko] undefined!
> > WARNING: modpost: Found 6 section mismatch(es).
> > To see full details build your kernel with:
> > 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> > make[1]: *** [__modpost] Error 1
> > make: *** [modules] Error 2
> >...
>
> Which gcc version are you using?
>
> Please send the complete .config
>
> cu
> Adrian
I'm going to compile it on 32-bit computer to try.
But I'd just suggest: why don't we add these functions __umoddi3 __udivdi3
and so to the kernel? This is not the first time I see it and it is pretty
annoying (and compiler- and optimization-dependent bug).
Mikulas
next prev parent reply other threads:[~2008-07-23 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 17:58 next-20080723: build fails for dm-snapshot.ko Thomas Meyer
2008-07-23 18:28 ` Adrian Bunk
2008-07-23 18:33 ` Mikulas Patocka [this message]
2008-07-23 18:43 ` Thomas Meyer
2008-07-23 20:51 ` Adrian Bunk
2008-07-23 21:16 ` [PATCHES] " Mikulas Patocka
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=Pine.LNX.4.64.0807231431250.3332@devserv.devel.redhat.com \
--to=mpatocka@redhat$(echo .)com \
--cc=bunk@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=thomas@m3y3r$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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