From: Randy Dunlap <randy.dunlap@oracle•com>
To: linux-next@vger•kernel.org
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
LKML <linux-kernel@vger•kernel.org>,
linux-media@vger•kernel.org
Subject: Re: linux-next: Tree for November 30 (media/common/tuners/max2165)
Date: Wed, 2 Dec 2009 10:04:06 -0800 [thread overview]
Message-ID: <20091202100406.e25b2322.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4B1409D9.1050901@oracle.com>
On Mon, 30 Nov 2009 10:07:21 -0800 Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20091127:
> >
> > The v4l-dvb tree lost its conflict.
>
>
> on i386 (X86_32):
>
> a 'double' variable is used, causing:
>
> ERROR: "__floatunsidf" [drivers/media/common/tuners/max2165.ko] undefined!
> ERROR: "__adddf3" [drivers/media/common/tuners/max2165.ko] undefined!
> ERROR: "__fixunsdfsi" [drivers/media/common/tuners/max2165.ko] undefined!
linux-next-20091202:
still have this one (above) and similar with
drivers/media/dvb/frontends/atbm8830.c:
drivers/built-in.o: In function `atbm8830_init':
atbm8830.c:(.text+0x9012f9): undefined reference to `__udivdi3'
atbm8830.c:(.text+0x901384): undefined reference to `__floatunsidf'
atbm8830.c:(.text+0x901395): undefined reference to `__muldf3'
atbm8830.c:(.text+0x9013a5): undefined reference to `__floatunsidf'
atbm8830.c:(.text+0x9013b2): undefined reference to `__divdf3'
atbm8830.c:(.text+0x9013c3): undefined reference to `__muldf3'
atbm8830.c:(.text+0x9013cd): undefined reference to `__fixunsdfsi'
---
~Randy
next prev parent reply other threads:[~2009-12-02 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 6:53 linux-next: Tree for November 30 Stephen Rothwell
2009-11-30 18:07 ` linux-next: Tree for November 30 (media/common/tuners/max2165) Randy Dunlap
2009-12-02 18:04 ` Randy Dunlap [this message]
2009-12-03 13:54 ` [PATCH] max2165 32bit build patch David T. L. Wong
2009-12-03 17:24 ` Randy Dunlap
2009-12-03 13:57 ` [PATCH] atbm8830: replace 64-bit division and floating point usage David T. L. Wong
2009-12-03 17:25 ` Randy Dunlap
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=20091202100406.e25b2322.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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