public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] start a linker script helper file
Date: Sun, 23 Aug 2009 22:41:02 +0200	[thread overview]
Message-ID: <20090823204102.B75D1833DBD2@gemini.denx.de> (raw)
In-Reply-To: <1251010079-10475-1-git-send-email-vapier@gentoo.org>

Dear Mike Frysinger,

In message <1251010079-10475-1-git-send-email-vapier@gentoo.org> you wrote:
> Start a common header file for common linker script code (such as
> workarounds for older linkers) rather than doing this in the build system.
> 
> As fallout, we no longer execute the linker every time config.mk is
> included by a build file (which can easily be 70+ times), but rather only
> execute it once.
> 
> This also fixes a bug in the major version checking by creating a macro to
> easily compare versions and keep people from making the same common
> mistake (forgetting to check major and minor together).
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> note: rather than update every linker script and add an #include, i forced
> it by using -include $(TOPDIR)/include/u-boot/u-boot.lds.h.  i think this
> is sane going forward.
> 
> also, i picked include/u-boot/ over include/asm-generic/ as the former
> seemed like a better u-boot-specific dir.  linux uses include/asm-generic/.
> doesnt matter much to me.
> 
>  Makefile                    |    8 ++++++++
>  config.mk                   |   10 ----------
>  include/u-boot/u-boot.lds.h |   25 +++++++++++++++++++++++++
>  3 files changed, 33 insertions(+), 10 deletions(-)
>  create mode 100644 include/u-boot/u-boot.lds.h

That's version 2, right?

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
Cogito cogito ergo cogito sum - "I think that I  think,  therefore  I
think that I am."          - Ambrose Bierce, "The Devil's Dictionary"

  reply	other threads:[~2009-08-23 20:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 12:00 [U-Boot] [PATCH] Fix all linker scripts for older binutils versions (pre-2.16) Wolfgang Denk
2009-08-17 19:14 ` Mike Frysinger
2009-08-17 19:31   ` Wolfgang Denk
2009-08-17 20:15     ` Mike Frysinger
2009-08-17 20:24       ` Wolfgang Denk
2009-08-17 20:31         ` Mike Frysinger
2009-08-21 21:14 ` Wolfgang Denk
2009-08-22 23:50 ` [U-Boot] [PATCH] Blackfin: use common code to preprocess linker script Mike Frysinger
2009-08-23 20:25   ` Wolfgang Denk
2009-08-23  0:00 ` [U-Boot] [PATCH] Fix all linker scripts for older binutils versions (pre-2.16) Mike Frysinger
2009-08-23  5:34   ` Wolfgang Denk
2009-08-23  6:09     ` Mike Frysinger
2009-08-23 19:30       ` Wolfgang Denk
2009-08-23  6:47     ` [U-Boot] [PATCH] start a linker script helper file Mike Frysinger
2009-08-23 20:41       ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-23  6:44 Mike Frysinger
2009-08-23  6:49 ` Mike Frysinger

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=20090823204102.B75D1833DBD2@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