From: Chris Ball <cjb@laptop.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Girish K S <girish.shivananjappa@linaro.org>,
linux-mmc@vger.kernel.org, kgene.kim@samsung.com,
patches@linaro.org, linux-samsung-soc@vger.kernel.org,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mmc: card: modify mmc_getgeo function
Date: Mon, 26 Sep 2011 08:41:13 -0400 [thread overview]
Message-ID: <m2k48vtr12.fsf@bob.laptop.org> (raw)
In-Reply-To: <20110926082814.GA28149@pengutronix.de> ("Uwe Kleine-König"'s message of "Mon, 26 Sep 2011 10:28:14 +0200")
Hi,
On Mon, Sep 26 2011, Uwe Kleine-König wrote:
>> Thanks, pushed to mmc-next for 3.2 with a reworded commit message:
> This (i.e. ee9e0e0 (mmc: card: Remove duplicated constants) in next)
> makes gcc emit a reference to __aeabi_uldivmod in one of my nightly
> builds which isn't defined.
>
> The final linking stage fails with:
>
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `mmc_blk_getgeo':
> clkdev.c:(.text+0xd1528): undefined reference to `__aeabi_uldivmod'
> make[2]: *** [.tmp_vmlinux1] Error 1
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
Interesting, thanks. It builds fine here on my (gcc-4.6) ARM toolchains.
Looking online, I think you're hitting an old gcc-4.3 bug?
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: card: modify mmc_getgeo function
Date: Mon, 26 Sep 2011 08:41:13 -0400 [thread overview]
Message-ID: <m2k48vtr12.fsf@bob.laptop.org> (raw)
In-Reply-To: <20110926082814.GA28149@pengutronix.de> ("Uwe Kleine-König"'s message of "Mon, 26 Sep 2011 10:28:14 +0200")
Hi,
On Mon, Sep 26 2011, Uwe Kleine-K?nig wrote:
>> Thanks, pushed to mmc-next for 3.2 with a reworded commit message:
> This (i.e. ee9e0e0 (mmc: card: Remove duplicated constants) in next)
> makes gcc emit a reference to __aeabi_uldivmod in one of my nightly
> builds which isn't defined.
>
> The final linking stage fails with:
>
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `mmc_blk_getgeo':
> clkdev.c:(.text+0xd1528): undefined reference to `__aeabi_uldivmod'
> make[2]: *** [.tmp_vmlinux1] Error 1
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
Interesting, thanks. It builds fine here on my (gcc-4.6) ARM toolchains.
Looking online, I think you're hitting an old gcc-4.3 bug?
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-09-26 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 11:08 [PATCH] mmc: card: modify mmc_getgeo function Girish K S
2011-09-21 18:52 ` Chris Ball
2011-09-26 8:28 ` Uwe Kleine-König
2011-09-26 8:28 ` Uwe Kleine-König
2011-09-26 12:41 ` Chris Ball [this message]
2011-09-26 12:41 ` Chris Ball
2011-09-26 13:09 ` Russell King - ARM Linux
2011-09-26 13:09 ` Russell King - ARM Linux
2011-09-26 13:13 ` Uwe Kleine-König
2011-09-26 13:13 ` Uwe Kleine-König
2011-09-26 13:19 ` Russell King - ARM Linux
2011-09-26 13:19 ` Russell King - ARM Linux
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=m2k48vtr12.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=girish.shivananjappa@linaro.org \
--cc=kernel@pengutronix.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.