From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Handle .gnu.hash section in ldscripts
Date: Thu, 13 Feb 2014 12:39:07 +0100 [thread overview]
Message-ID: <20140213123907.6b97040e@lilith> (raw)
In-Reply-To: <52E6A96B.1080002@suse.de>
Hi Andreas,
On Mon, 27 Jan 2014 19:46:03 +0100, Andreas F?rber <afaerber@suse.de>
wrote:
> Hello,
>
> Am 27.01.2014 15:24, schrieb Wolfgang Denk:
> > In message <1390798091-24747-1-git-send-email-afaerber@suse.de> you wrote:
> >> Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE.
> >>
> >> Cc: Albert Aribaud <albert.u.boot@aribaud.net>
> >> Cc: Tom Rini <trini@ti.com>
> >> Signed-off-by: Andreas F?rber <afaerber@suse.de>
> >> ---
> >> More changes like this may be needed, but these I compile-tested with
> >> v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested.
> >> GCC 4.8.2 r206511, binutils 2.24
> >>
> >> arch/arm/cpu/u-boot.lds | 1 +
> >> board/ti/am335x/u-boot.lds | 1 +
> >> 2 files changed, 2 insertions(+)
> >
> > Is this an ARM specific issue, or other architectures affected as
> > well?
>
> I figured out that the section was apparently not caught by the .gnu*
> wildcard and this patch fixed our build for the following ARM configs:
>
> am335x_evm
> arndale
> colibri_t20_iris
> cubieboard
> highbank
> hyundai_a7hd
> mele_a1000
> mx53loco
> omap3_beagle
> omap4_panda
> paz00
> rpi_b
>
> My guess was that this could be related to the arm-only commit:
> http://git.denx.de/?p=u-boot.git;a=commit;h=47ed5dd031d7d2c587e6afd386e79ccec1a1b7f7
> (which touches on a few more .lds files than mine)
>
> But I see nothing ARM-specific in .gnu.hash sections, so other
> architectures might in theory be affected as well.
> Cf. http://sourceware.org/ml/binutils/2006-10/msg00377.html
>
> I did read your post for ELDK pointing someone to an FAQ entry on not
> using gcc-specific flags with ld, but for one I did not spot such a
> thing in the ld command line, and for another our toolchain did not
> change and v2013.10 builds succeed whereas v2014.01 builds failed
> without the patch. I could try to git-bisect the offending change if
> necessary.
Using gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7), I cannot see
any issues on these boards:
am335x_evm
colibri_t20_iris
highbank
mx53loco
omap3_beagle
omap4_panda
paz00
rpi_b
On arndale, issues are due to warnings unrelated to linking.
Cubieboard, hyundai_a7hd, mele_a1000 are not in mainline AFAICT (but I'd
like to see mele_a1000 in, as this might mean mele_a1000g could
follow. :) )
Can you point me to the toolchain you are using, and if you are not
building mainline code, can you make this code available to me somehow?
> Best regards,
>
> Andreas
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-02-13 11:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 4:48 [U-Boot] [PATCH] arm: Handle .gnu.hash section in ldscripts Andreas Färber
2014-01-27 14:24 ` Wolfgang Denk
2014-01-27 18:46 ` Andreas Färber
2014-01-27 19:11 ` Wolfgang Denk
2014-01-28 14:01 ` Andreas Färber
2014-01-28 16:03 ` Wolfgang Denk
2014-02-13 11:39 ` Albert ARIBAUD [this message]
2014-02-22 13:27 ` Albert ARIBAUD
2014-03-02 17:57 ` Andreas Färber
2014-03-02 19:15 ` Albert ARIBAUD
2014-03-02 20:57 ` Andreas Färber
2014-03-02 22:00 ` Andreas Färber
2014-03-02 23:44 ` Tom Rini
2014-03-03 6:58 ` Albert ARIBAUD
2014-03-03 7:00 ` Albert ARIBAUD
2014-03-09 20:05 ` Albert ARIBAUD
2014-03-09 20:22 ` Andreas Färber
2014-03-09 20:34 ` Albert ARIBAUD
2014-03-09 20:52 ` Andreas Färber
2014-03-10 7:24 ` Albert ARIBAUD
2014-03-13 15:43 ` Lukasz Majewski
2014-03-13 17:37 ` Albert ARIBAUD
2014-03-14 7:37 ` Lukasz Majewski
2014-03-19 9:33 ` Albert ARIBAUD
2014-03-03 8:41 ` Richard Biener
2014-03-03 13:25 ` Tom Rini
2014-03-25 2:08 ` Simon Glass
2014-04-07 9:43 ` Albert ARIBAUD
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=20140213123907.6b97040e@lilith \
--to=albert.u.boot@aribaud.net \
--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;
as well as URLs for NNTP newsgroup(s).