From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] config.mk: move LDSCRIPT processing to the top-level Makefile
Date: Wed, 22 Jun 2011 20:05:16 +0200 [thread overview]
Message-ID: <20110622180516.D274E13D91CD@gemini.denx.de> (raw)
In-Reply-To: <1308609939-23337-1-git-send-email-yanok@emcraft.com>
Dear Ilya Yanok,
In message <1308609939-23337-1-git-send-email-yanok@emcraft.com> you wrote:
> LDSCRIPT is used only from the top-level Makefile and only when the
> system is configured so we can move LDSCRIPT and CONFIG_SYS_LDSCRIPT
> related logic into the top level Makefile and under configured condition
> to avoid errors when building tools from unconfigured tree.
>
> Signed-off-by: Ilya Yanok <yanok@emcraft.com>
> ---
> Makefile | 30 ++++++++++++++++++++++++++++++
> config.mk | 30 ------------------------------
> 2 files changed, 30 insertions(+), 30 deletions(-)
Applied, thanks.
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
Don't panic.
prev parent reply other threads:[~2011-06-22 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 22:45 [U-Boot] [PATCH 1/3] config.mk: move LDSCRIPT processing to the top-level Makefile Ilya Yanok
2011-06-20 22:45 ` [U-Boot] [PATCH 2/3] Makefile: move $(VERSION_FILE) rule out of ifeq configured Ilya Yanok
2011-06-21 1:57 ` Mike Frysinger
2011-06-20 22:45 ` [U-Boot] [PATCH 3/3] tools/Makefile: fix errors during deps generation for envcrc Ilya Yanok
2011-06-21 1:58 ` Mike Frysinger
2011-06-22 18:05 ` Wolfgang Denk
2011-06-21 1:57 ` [U-Boot] [PATCH 1/3] config.mk: move LDSCRIPT processing to the top-level Makefile Mike Frysinger
2011-06-22 18:05 ` Wolfgang Denk [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=20110622180516.D274E13D91CD@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