From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Introduce a new linker flag LDFLAGS_FINAL
Date: Tue, 01 Feb 2011 08:34:01 +0100 [thread overview]
Message-ID: <20110201073401.1B343B187@gemini.denx.de> (raw)
In-Reply-To: <20110131135548.50d65759@udp111988uds.am.freescale.net>
Dear Scott Wood,
In message <20110131135548.50d65759@udp111988uds.am.freescale.net> you wrote:
>
> > [Btw: "final" is probably not a technically correct term for all the
> > use cases I see below.]
>
> I meant final as compared to partial links, not anything to do with spl
> versus tpl versus the main image.
>
> Do you have a better wording?
Not really. ld documentation also talks about "final binary" or "final
executable". Note that I'm not insisting on a change here.
> > > LDFLAGS += $(PLATFORM_LDFLAGS)
> > > +LDFLAGS_FINAL += -Bstatic $(LDFLAGS)
> > >
> > > -LDFLAGS_u-boot += -Bstatic -T $(obj)u-boot.lds $(PLATFORM_LDFLAGS)
> > > +LDFLAGS_u-boot += -T $(obj)u-boot.lds $(LDFLAGS_FINAL)
> >
> > Is it intentional that you change PLATFORM_LDFLAGS into LDFLAGS here?
> >
> > Are you sure that this change is correct for all affected boards?
> >
> > How has this change been tested?
>
> As I understand it, it has only been limited to PLATFORM_LDFLAGS since
> the LDFLAGS_u-boot commit. Was that change intentional, and widely
> tested?
Can you please be more specific? I don't see where "the
LDFLAGS_u-boot commit" (you mean 8aba9dc ?) would change any related
code. The relevant hunk looks like this:
@@ -204,9 +204,11 @@ endif
AFLAGS := $(AFLAGS_DEBUG) -D__ASSEMBLY__ $(CPPFLAGS)
-LDFLAGS += -Bstatic -T $(obj)u-boot.lds $(PLATFORM_LDFLAGS)
+LDFLAGS += $(PLATFORM_LDFLAGS)
+
+LDFLAGS_u-boot += -Bstatic -T $(obj)u-boot.lds $(PLATFORM_LDFLAGS)
ifneq ($(CONFIG_SYS_TEXT_BASE),)
-LDFLAGS += -Ttext $(CONFIG_SYS_TEXT_BASE)
+LDFLAGS_u-boot += -Ttext $(CONFIG_SYS_TEXT_BASE)
endif
# Location of a usable BFD library, where we define "usable" as
and this does not make any changes of PLATFORM_LDFLAGS into LDFLAGS
or vice versa.
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
"...all the good computer designs are bootlegged; the formally
planned products, if they are built at all, are dogs!" - David E.
Lundstrom, "A Few Good Men From Univac", MIT Press, 1987
next prev parent reply other threads:[~2011-02-01 7:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 18:32 [U-Boot] [PATCH] Introduce a new linker flag LDFLAGS_FINAL Haiying.Wang at freescale.com
2011-01-31 19:33 ` Wolfgang Denk
2011-01-31 19:55 ` Scott Wood
2011-02-01 7:34 ` Wolfgang Denk [this message]
2011-02-01 14:59 ` Haiying Wang
2011-02-01 16:24 ` Scott Wood
2011-02-01 19:32 ` Wolfgang Denk
2011-02-01 19:51 ` Scott Wood
2011-02-01 20:20 ` Wolfgang Denk
2011-02-01 20:40 ` Scott Wood
2011-02-04 15:52 ` Haiying Wang
2011-02-15 9:02 ` Mike Frysinger
2011-02-16 0:51 ` Scott Wood
2011-02-17 5:01 ` Mike Frysinger
2011-02-04 22:56 ` Graeme Russ
2011-01-31 20:14 ` Haiying Wang
2011-01-31 20:30 ` Wolfgang Denk
[not found] ` <1297878184.1977.18.camel@haiying-laptop>
2011-02-16 18:29 ` Wolfgang Denk
2011-02-16 18:40 ` Haiying Wang
2011-02-16 18:58 ` Wolfgang Denk
2011-02-17 5:37 ` Mike Frysinger
2011-02-17 8:33 ` Wolfgang Denk
2011-02-17 19:28 ` Haiying Wang
2011-02-17 20:38 ` Haiying Wang
2011-02-22 19:39 ` 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=20110201073401.1B343B187@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