From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Non-static global variables cause relocation to fail
Date: Thu, 19 Jun 2008 22:52:47 +0200 [thread overview]
Message-ID: <20080619205247.10F95248D2@gemini.denx.de> (raw)
In-Reply-To: Your message of "Thu, 19 Jun 2008 15:47:01 CDT." <485AC5C5.5080709@freescale.com>
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.
Also, there are several tool chains being used.
You provide NONE of that *essential* information.
> Works:
>
> static struct __attribute__ ((__packed__)) eeprom {
>
> Doesn't work:
>
> struct __attribute__ ((__packed__)) eeprom {
>
> Everything else is the same.
What is "same"? Which source file is this? Which line? Which board?
Which compiler from which distro? Which binutils?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It is undignified for a woman to play servant to a man who is not
hers.
-- Spock, "Amok Time", stardate 3372.7
next prev parent reply other threads:[~2008-06-19 20:52 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 [this message]
2008-06-19 21:12 ` Timur Tabi
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=20080619205247.10F95248D2@gemini.denx.de \
--to=wd@denx.de \
--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