All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Handle .gnu.hash section in ldscripts
Date: Fri, 14 Mar 2014 08:37:00 +0100	[thread overview]
Message-ID: <20140314083700.13dcaf7a@amdc2363> (raw)
In-Reply-To: <E1WO9Zp-00038U-I8@janus>

Hi Albert,

> Hi Lukasz,
> 
> On Thu, 13 Mar 2014 16:43:09 +0100, Lukasz Majewski
> <l.majewski@samsung.com> wrote:
> 
> > I can report the same issue with OBS build of u-boot.
> > 
> > When u-boot is build with qemu emulated environment with gcc-4.8.2
> > (native armv7l toolchain) in the OBS it needs patch prepared by
> > Andreas.
> 
> Hmm, ok, so maybe I can reproduce this by building U-Boot on native
> armv7 hardware. Any target which systematically fails building?

The Trats2 fails to be build. But to me it seems like compiler and
linker issue.

> 
> > However I can build the same code from u-boot directory (without
> > this patch) with following toolchain:
> > arm-v7a-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.0
> > linaro-4.8-2013.11) 4.8.3 20131111
> 
> Hmm... So it depends on the toolchain.
> 
> > Any ideas how to solve this?
> 
> Are both toolchains you used available somewhere so that I can fetch
> them and experiment locally?

Yes they are available. References below:

arm-v7a-linux-gnueabi-gcc
(OSELAS.Toolchain-2013.12.0linaro-4.8-2013.11) 4.8.3 20131111
linaro-4.8-2013.11) 4.8.3 20131111
http://www.ptxdist.org/software/ptxdist/index_en.html


The one which is used in the OBS:
gcc-4.8-2.56.armv7l.rpm

can be download from:
http://download.tizen.org/snapshots/tizen/rd-pq/latest/repos/mobile/armv7l/packages/armv7l/

I hope, that it helps.

> 
> Amicalement,



-- 
Best regards,

Lukasz Majewski

Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

  reply	other threads:[~2014-03-14  7:37 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 [this message]
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=20140314083700.13dcaf7a@amdc2363 \
    --to=l.majewski@samsung.com \
    --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.