public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Non-static global variables cause relocation to fail
Date: Thu, 19 Jun 2008 16:12:52 -0500	[thread overview]
Message-ID: <485ACBD4.8030608@freescale.com> (raw)
In-Reply-To: <20080619205247.10F95248D2@gemini.denx.de>

Wolfgang Denk wrote:
> In message <485AC5C5.5080709@freescale.com> you wrote:
>> I did say that.  Simply making the global variable not static caused it to fail.
> 
> Ummm... I guess there must be more than one variable in U-Boot, as
> there are several source files and several board configurations.

Sorry, I was under the assumption that the problem is not unique to the actual
variable in question.  That is, making any global variable non-static risks
having relocation fail.

I was looking for a more general explanation to the problem.  I was hoping that
someone who understood the relocation code well could explain to me, in
theoretical terms, how this could happen.

> What is "same"? Which source file is this? Which line?  Which  board?
> Which compiler from which distro? Which binutils?

This is a new file that I haven't posted yet.  It is a replacement for
board/freescale/common/sys_eeprom.c.  It's currently undergoing internal review.
 That's why I asked for a general explanation.

Compiler: powerpc-linux-gnu-gcc (GCC) 4.2.1
Binutils: GNU ld (GNU Binutils) 2.18.50.20070820

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-06-19 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 18:44 [U-Boot-Users] Non-static global variables cause relocation to fail Timur Tabi
2008-06-19 20:45 ` Wolfgang Denk
2008-06-19 20:47   ` Timur Tabi
2008-06-19 20:52     ` Wolfgang Denk
2008-06-19 21:12       ` Timur Tabi [this message]
2008-06-19 21:55         ` Wolfgang Denk
2008-06-20  3:33     ` Jerry Van Baren
2008-06-20 14:47       ` Timur Tabi
2008-06-21  0:27         ` Wolfgang Denk
2008-06-22 17:17         ` Jerry Van Baren

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=485ACBD4.8030608@freescale.com \
    --to=timur@freescale.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