From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman: arm: undefined reference to `__aeabi_ldivmod'
Date: Mon, 14 Mar 2016 12:14:14 -0600 [thread overview]
Message-ID: <56E6FF76.6040706@wwwdotorg.org> (raw)
In-Reply-To: <CAD6G_RRV6iBrwTB_vJBt=N0cnAngugcAVa_YHZLNWVuL9NuG4w@mail.gmail.com>
On 03/14/2016 11:32 AM, Jagan Teki wrote:
> Hi Simon,
>
> On 12 March 2016 at 06:02, Simon Glass <sjg@chromium.org> wrote:
>> +Stephen
>>
>> Hi Jagan,
>>
>> On 11 March 2016 at 01:00, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> Did anyone encounter this issue? please let me know for any inputs.
>>>
>>> arm: + venice2
>>> +drivers/mtd/spi-nor/built-in.o: In function `spi_nor_write':
>>> +build/../drivers/mtd/spi-nor/spi-nor.c:585: undefined reference to
>>> `__aeabi_ldivmod'
>>> +arm-unknown-linux-gnueabi-ld.bfd: BFD (GNU Binutils) 2.24 assertion
>>> fail /home/tony/buildall/src/binutils/bfd/elf32-arm.c:7696
>>> +arm-unknown-linux-gnueabi-ld.bfd: error: required section '.rel.plt'
>>> not found in the linker script
>>> +arm-unknown-linux-gnueabi-ld.bfd: final link failed: Invalid operation
>>> +make[1]: *** [u-boot] Error 1
>>> +make: *** [sub-make] Error 2
>>
>> Are you using 64-bit division? Tegra uses the private libgcc. This
>> patch might help:
>
> Yes, I'm using 64-bit.
>
>> http://patchwork.ozlabs.org/patch/592628/
>
> Still the same issue.
If I start with v2016.03, and apply the following patch, I can reproduce
this issue when building venice2 (a 32-bit Tegra build) but not
p2371-2180 (a 64-bit Tegra build):
diff --git a/arch/arm/mach-tegra/board2.c b/arch/arm/mach-tegra/board2.c
index ac274e17e8bd..9b1a4112a0b1 100644
--- a/arch/arm/mach-tegra/board2.c
+++ b/arch/arm/mach-tegra/board2.c
@@ -235,9 +235,13 @@ __weak void pin_mux_mmc(void)
{
}
+uint64_t a = 200;
+uint64_t b = 5;
+
/* this is a weak define that we are overriding */
int board_mmc_init(bd_t *bd)
{
+ printf("a/b = %llu\n", a / b);
debug("%s called\n", __func__);
/* Enable muxes, etc. for SDMMC controllers */
However, if I apply the patch Simon mentioned above, the problem is
fixed. Are you sure you applied that patch correctly?
next prev parent reply other threads:[~2016-03-14 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 8:00 [U-Boot] buildman: arm: undefined reference to `__aeabi_ldivmod' Jagan Teki
2016-03-12 0:32 ` Simon Glass
2016-03-14 17:32 ` Jagan Teki
2016-03-14 18:14 ` Stephen Warren [this message]
2016-03-16 14:27 ` Jagan Teki
2016-03-16 15:34 ` Stephen Warren
2016-03-17 5:48 ` Jagan Teki
2016-03-17 16:18 ` Stephen Warren
2016-05-01 23:12 ` Simon Glass
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=56E6FF76.6040706@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox