From: Guenter Roeck <linux@roeck-us.net>
To: Meelis Roos <mroos@linux.ee>
Cc: linuxppc-dev@lists.ozlabs.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: 3.11-rc3+git: __divdi3 undefined on powerpc (from radeon)
Date: Sun, 4 Aug 2013 08:49:43 -0700 [thread overview]
Message-ID: <20130804154943.GA13807@roeck-us.net> (raw)
In-Reply-To: <alpine.SOC.1.00.1308031534390.1352@math.ut.ee>
On Sat, Aug 03, 2013 at 03:44:26PM +0300, Meelis Roos wrote:
> While trying to compile v3.11-rc3-288-gabe0308 on powerpc 32-bit,
> it failed with the following linking error:
>
> ERROR: "__divdi3" [drivers/gpu/drm/radeon/radeon.ko] undefined!
>
> Some new 64-bit division in radeon that is not implemented on 32-bit
> powerpc?
>
> This is new - 3.11-rc3 worked fine.
>
Not only powerpc - i386 builds fail with the same error.
Guenter
prev parent reply other threads:[~2013-08-04 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 12:44 3.11-rc3+git: __divdi3 undefined on powerpc (from radeon) Meelis Roos
2013-08-03 13:52 ` Alex Deucher
2013-08-04 15:49 ` Guenter Roeck [this message]
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=20130804154943.GA13807@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mroos@linux.ee \
/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).