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 15:47:01 -0500 [thread overview]
Message-ID: <485AC5C5.5080709@freescale.com> (raw)
In-Reply-To: <20080619204505.48ABD248D2@gemini.denx.de>
Wolfgang Denk wrote:
> You don't seriously expect any real help given such a vague
> description? It would be somewhat helpful if you said exactly which
> changes cause the code to work or fail...
I did say that. Simply making the global variable not static caused it to fail.
Works:
static struct __attribute__ ((__packed__)) eeprom {
Doesn't work:
struct __attribute__ ((__packed__)) eeprom {
Everything else is the same.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-06-19 20:47 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 [this message]
2008-06-19 20:52 ` Wolfgang Denk
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=485AC5C5.5080709@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