From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README.commands: Document what UNDEF_SYM does
Date: Wed, 19 Sep 2012 14:17:35 -0700 [thread overview]
Message-ID: <20120919211735.GH12703@bill-the-cat> (raw)
In-Reply-To: <505A34A4.2090509@myspectrum.nl>
On Wed, Sep 19, 2012 at 11:09:56PM +0200, Jeroen Hofstee wrote:
> On 09/19/2012 01:42 AM, Tom Rini wrote:
> >+To ensure that the linker does not discard these symbols when linking
> >+full U-Boot we use generate a list of all of the commands and force the
> >+linker to first enter the symbol as undefined in the object so that
> >+there is then a need for the symbol to be kept (UNDEF_SYM in the
> >+Makefile).
> >+
> I have no idea what this is about, but my mind has difficulty parsing
> this sentence.
>
> "To ensure that the linker does not discard these symbols when linking
> full U-Boot we use generate a list"
>
> a generated list?
Bah, re-wrote the sentance a few times in my head as I was writing it.
... full U-Boot we geneate a list of all the commands we have built
(based on the sections mentioned above) and use that to force the linker
...
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120919/e6e15e13/attachment.pgp>
prev parent reply other threads:[~2012-09-19 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 23:42 [U-Boot] [PATCH] README.commands: Document what UNDEF_SYM does Tom Rini
2012-09-19 21:09 ` Jeroen Hofstee
2012-09-19 21:17 ` Tom Rini [this message]
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=20120919211735.GH12703@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