public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Allow board specific overwriting of library code
Date: Wed, 04 Feb 2009 09:48:09 -0500	[thread overview]
Message-ID: <4989AAA9.4030100@ge.com> (raw)
In-Reply-To: <1233757799-1165-2-git-send-email-mroth@nessie.de>

Michael Roth wrote:
> Enables to overwrite any library code by defining EXTRABOARDOBJS
> in the board specific config.mk.
> Those listed object files get linked directly into the u-boot binary
> right after the start objects and before any archives.
> 
> Signed-off-by: Michael Roth <mroth@nessie.de>

Hi Michael,

Sorry for not speaking up sooner, but the term "overwrite" had really 
bad connotations (implies you are smashing the library).  "Override" is 
a much better term for what you are doing.

FWIIW, I don't have experience with "weak" functions, but I've seen the 
struggles of others on this email list.  My understanding is that you 
are getting gcc (the linker, actually) to behave much more as a 
developer expects when he needs to override a weak function.  (Current 
gcc behavior makes sense to the gcc folks, but tends to surprise mere 
mortals.  The principle of least astonishment[1] says this is a problem.)

Thanks,
gvb

[1] <http://en.wikipedia.org/wiki/Principle_of_least_astonishment>

  parent reply	other threads:[~2009-02-04 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 14:29 [U-Boot] [PATCH 0/2] Initial Stamp9261 board support Michael Roth
2009-02-04 14:29 ` [U-Boot] [PATCH 1/2] Allow board specific overwriting of library code Michael Roth
2009-02-04 14:29   ` [U-Boot] [PATCH 2/2] Stamp9261 board support Michael Roth
2009-02-04 16:05     ` Wolfgang Denk
2009-02-05 14:07       ` Michael Roth
2009-02-04 14:48   ` Jerry Van Baren [this message]
2009-02-04 15:36   ` [U-Boot] [PATCH 1/2] Allow board specific overwriting of library code Wolfgang Denk
2009-02-04 16:00     ` Michael Roth
2009-02-04 16:08       ` Wolfgang Denk
2009-02-04 16:18       ` Michael Roth
2009-02-04 16:23         ` Mike Frysinger
2009-02-04 21:12         ` 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=4989AAA9.4030100@ge.com \
    --to=gerald.vanbaren@ge.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