mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hylands <dhylands@gmail.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-fbdev@vger.kernel.org,
	Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: drivers/gpu/drm/radeon/radeon_test.c:45: undefined reference to  `__udivdi3'
Date: Sat, 19 Dec 2009 01:13:11 -0800	[thread overview]
Message-ID: <c32efac40912190113i5292a395tcc257c16a4870f3b@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.0912181147200.9874@filesrv1.baby-dragons.com>

Hi Jim,

On Fri, Dec 18, 2009 at 12:54 PM, Mr. James W. Laferriere
<babydr@baby-dragons.com> wrote:
>        Hello Benjamin ,  I am not having a good time compiling 2.6.32.1 .
> First RCU 'inline' difficulties then fusion-mpt 'inline' difficulty ,  Now
> this .
>        This one is not a simple as removing 'inline' from a statement .
>        Would you please look into this ?  Anything else you need please just
> ask .
>        Please cc: me as I am not subscribed to linux-fbdev .
>
>                Tia ,  JimL
>
...snip...
> drivers/built-in.o(.text+0x11345a): In function `radeon_test_moves':
> drivers/gpu/drm/radeon/radeon_test.c:45: undefined reference to `__udivdi3'
> make: *** [.tmp_vmlinux1] Error 1

__udivdi3 is a gcc helper function used to do 64-bit division. This
form of 64-bit division is not supported from within the kernel (which
is why you get the undefined symbol).

There is <asm/div64.h> which contains a macro called do_div which can
perform a 64-bit dvision by a 32-bit divisor.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

  reply	other threads:[~2009-12-19  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 20:54 Mr. James W. Laferriere
2009-12-19  9:13 ` Dave Hylands [this message]
2009-12-20  1:02   ` Mr. James W. Laferriere
2009-12-20  2:07     ` Dave Hylands
2009-12-20  6:11 ` Dave Airlie
2009-12-20 21:10   ` Mr. James W. Laferriere

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=c32efac40912190113i5292a395tcc257c16a4870f3b@mail.gmail.com \
    --to=dhylands@gmail.com \
    --cc=babydr@baby-dragons.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®