From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman: arm: undefined reference to `__aeabi_ldivmod'
Date: Thu, 17 Mar 2016 10:18:09 -0600 [thread overview]
Message-ID: <56EAD8C1.9080707@wwwdotorg.org> (raw)
In-Reply-To: <CAD6G_RSyFj7mhegydvGC2JDAfCC9zabXprad7ymqYuYYXTnWdg@mail.gmail.com>
On 03/16/2016 11:48 PM, Jagan Teki wrote:
> On 16 March 2016 at 21:04, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 03/16/2016 08:27 AM, Jagan Teki wrote:
>>> On 14 March 2016 at 23:44, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>>> On 03/14/2016 11:32 AM, Jagan Teki wrote:
>>>>> On 12 March 2016 at 06:02, Simon Glass <sjg@chromium.org> wrote:
>>>>>> On 11 March 2016 at 01:00, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>>>>>> 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/
...
>> Perhaps you could share the local patches that are triggering the problem?
...
> This is the spi-nor.c file
> http://git.denx.de/?p=u-boot/u-boot-spi.git;a=blob;f=drivers/mtd/spi-nor/spi-nor.c;h=6166b62e595c6620bd3407788d705168e0bd6b2c;hb=refs/heads/spi-nor-test
I can reproduce this when building venice2 in u-boot-spi/spi-nor-test,
and indeed the patch that Simon linked to doesn't help. That's because
Simon's patch implements __aeabi_uldivmod whereas the linker failure is
due to __aeabi_ldivmod (without the u).
Simon, is it easy for you to bring in __aeabi_ldivmod from the same place?
FWIW, I hacked _uldivmod.S to provide a dummy symbol for __aeabi_ldivmod
and the link succeeded, so I think that's currently the only missing
symbol. I only tested the venice2 build though.
next prev parent reply other threads:[~2016-03-17 16:18 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
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 [this message]
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=56EAD8C1.9080707@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