From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kbuild: fix SPL link bug when USE_PRIVATE_LIBGCC is "yes"
Date: Mon, 24 Feb 2014 11:02:25 -0700 [thread overview]
Message-ID: <530B8931.2040106@wwwdotorg.org> (raw)
In-Reply-To: <1393242254-19189-1-git-send-email-yamada.m@jp.panasonic.com>
On 02/24/2014 04:44 AM, Masahiro Yamada wrote:
> Commit 6825a95 (kbuild: use Linux Kernel build scripts)
> changed the behavior of linkage when USE_PRIAVATE_LIBGCC
> is defined as "yes".
> (It dropped arch/arm/lib/eabi_compat.o from the
> target library.)
>
> Affected boards are all Tegra boards.
>
> This commit gets back the same behavior as before Kbuild series.
Tested-by: Stephen Warren <swarren@nvidia.com>
... although interestingly, at least with the Ubuntu 12.10 ARM
cross-compiler, the resultant U-Boot works fine with or without this
patch. I'd have expected it to fail without this patch since it sounds
like USE_PRIVATE_LIBGCC might not be honored correctly, but perhaps the
linker cmdline order works out such that the custom libgcc happens to be
picked up anyway, just not in the way intended.
next prev parent reply other threads:[~2014-02-24 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 11:44 [U-Boot] [PATCH] kbuild: fix SPL link bug when USE_PRIVATE_LIBGCC is "yes" Masahiro Yamada
2014-02-24 18:02 ` Stephen Warren [this message]
2014-02-25 0:24 ` Masahiro Yamada
2014-02-25 13:58 ` [U-Boot] " Tom Rini
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=530B8931.2040106@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