All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 7 Apr 2014 11:43:21 +0200	[thread overview]
Message-ID: <E1WX65K-0004jf-Gz@janus> (raw)
In-Reply-To: <1390798091-24747-1-git-send-email-afaerber@suse.de>

Hi Andreas,

On Mon, 27 Jan 2014 05:48:11 +0100, Andreas F?rber <afaerber@suse.de>
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(+)
> 
> diff --git a/arch/arm/cpu/u-boot.lds b/arch/arm/cpu/u-boot.lds
> index 4da5d24..fb8bfaf 100644
> --- a/arch/arm/cpu/u-boot.lds
> +++ b/arch/arm/cpu/u-boot.lds
> @@ -97,6 +97,7 @@ SECTIONS
>  	.dynamic : { *(.dynamic*) }
>  	.plt : { *(.plt*) }
>  	.interp : { *(.interp*) }
> +	.gnu.hash : { *(.gnu.hash) }
>  	.gnu : { *(.gnu*) }
>  	.ARM.exidx : { *(.ARM.exidx*) }
>  	.gnu.linkonce.armexidx : { *(.gnu.linkonce.armexidx.*) }
> diff --git a/board/ti/am335x/u-boot.lds b/board/ti/am335x/u-boot.lds
> index 6a734b3..fec4ccf 100644
> --- a/board/ti/am335x/u-boot.lds
> +++ b/board/ti/am335x/u-boot.lds
> @@ -113,6 +113,7 @@ SECTIONS
>  	.dynstr : { *(.dynstr*) }
>  	.dynamic : { *(.dynamic*) }
>  	.hash : { *(.hash*) }
> +	.gnu.hash : { *(.gnu.hash) }
>  	.plt : { *(.plt*) }
>  	.interp : { *(.interp*) }
>  	.gnu : { *(.gnu*) }

Applied to u-boot-arm/master, thanks!

Amicalement,
-- 
Albert.

      parent reply	other threads:[~2014-04-07  9:43 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
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 [this message]

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=E1WX65K-0004jf-Gz@janus \
    --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 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.