public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Relocation issue - need help!
Date: Wed, 22 Oct 2014 13:28:11 -0400	[thread overview]
Message-ID: <20141022172811.GD25506@bill-the-cat> (raw)
In-Reply-To: <20141022165611.ED5203832AC@gemini.denx.de>

On Wed, Oct 22, 2014 at 06:56:11PM +0200, Wolfgang Denk wrote:
> Dear Dirk,
> 
> In message <CANVMifLGzKz+=-K-E9_sSXBxpYPdG1YqEXc-tsCApi7WVxQAHg@mail.gmail.com> you wrote:
> > I had exactly the same behaviour some time ago and tracked it down to
> > this (and posted it on the mailing list, but sadly got no feedback):
> 
> Thanks a lot for this pointer.
> 
> > So there a three things to notice:
> > 1. Do not use gcc 4.8 and u-boot at the moment.
> > 2. You might not notice that you have a problem until you erase u-boot
> > from flash (and get your cache flushed).
> > 3. Handling relro properly should be on the TODO-List
> 
> I confirm that the problem is in my case with gcc 4.8.1, too.  I did
> not try another compiler yet.
> 
> > Maybe this is already common knowledge an maybe somebody is already
> > working on this - but I did not notice yet. So in this case: sorry for
> > the noise :)
> 
> I highly appreciate your hint, it was definitely very useful. Thanks!

Is this ARM or PowerPC?  The kernel has blacklisted 4.8.x for ARM in
some cases, and this may or may not be related (see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854)

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141022/e02b7832/attachment.pgp>

  parent reply	other threads:[~2014-10-22 17:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 12:39 [U-Boot] Relocation issue - need help! Wolfgang Denk
2014-10-22 13:29 ` Dirk Eibach
2014-10-22 16:56   ` Wolfgang Denk
2014-10-22 17:26     ` Fabio Estevam
2014-10-22 17:28     ` Tom Rini [this message]
2014-10-22 17:39       ` Wolfgang Denk
2014-10-22 21:27       ` Pavel Machek
2014-10-22 21:46         ` Marek Vasut
2014-10-22 21:57           ` Pavel Machek
2014-10-22 22:06             ` Marek Vasut
2014-10-23  6:01     ` Dirk Eibach
2014-10-23  6:42       ` Joakim Tjernlund
2014-10-23 13:10         ` Wolfgang Denk
2014-10-23 13:42           ` Dirk Eibach
2014-10-24 14:14           ` Bill Pringlemeir
2015-09-30 18:24           ` Andy Fleming
2015-09-30 19:35             ` Marek Vasut
2015-10-01  8:57               ` Joakim Tjernlund
2015-10-06 11:17                 ` Joakim Tjernlund
2015-10-15 15:56                   ` Joakim Tjernlund
2015-10-15 21:58                     ` Tom Rini
2015-10-16  6:55                       ` Joakim Tjernlund
2015-10-16 11:47                         ` Tom Rini
2015-10-16 13:14                           ` Joakim Tjernlund
2015-10-20 21:06                             ` Andy Fleming
2015-10-20 21:21                               ` Tom Rini
2015-10-21  8:44                                 ` Joakim Tjernlund
2015-10-21 13:12                                   ` Tom Rini
2015-10-21 13:18                                     ` Joakim Tjernlund
2015-10-01 14:18             ` Wolfgang Denk
2015-10-02 22:51               ` Andy Fleming
2015-10-03  8:33                 ` Wolfgang Denk

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=20141022172811.GD25506@bill-the-cat \
    --to=trini@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox