From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: make it possible to build tools unconfigured
Date: Sat, 18 Jun 2011 16:21:44 -0400 [thread overview]
Message-ID: <201106181621.46436.vapier@gentoo.org> (raw)
In-Reply-To: <20110618201117.2C37D19E5AC9@gemini.denx.de>
On Saturday, June 18, 2011 16:11:17 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > pretty sure this breaks board builds. if the only thing this fixes is a
> > harmless warning when generating dependency files, then i say ignore it.
> > after all, this is how it has always worked in the past and no one really
> > cared.
>
> There have been no warnings when generating dependencies.
yes, there has. you probably dont run `make tools` (at least, in an
unconfigured tree), so you've never noticed.
> Changes that cause new warnings need to be fixed.
you'll have to define "new" here. the warning he refers to has been there for
many many releases, and for pretty much as long as i can remember.
i dont mind fixing warnings, but i do mind breaking the building of boards to
fix a harmless warning.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110618/a0b40352/attachment.pgp
next prev parent reply other threads:[~2011-06-18 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 21:37 [U-Boot] [PATCH] tools: make it possible to build tools unconfigured Ilya Yanok
2011-06-18 19:03 ` Mike Frysinger
2011-06-18 20:11 ` Wolfgang Denk
2011-06-18 20:21 ` Mike Frysinger [this message]
2011-06-19 17:55 ` Ilya Yanok
2011-06-19 18:27 ` Mike Frysinger
2011-06-19 22:46 ` Ilya Yanok
2011-06-19 23:22 ` Mike Frysinger
2011-06-20 17:52 ` Scott Wood
2011-10-17 19:42 ` Wolfgang Denk
2011-10-17 20:24 ` Ilya Yanok
2011-10-17 20:35 ` Wolfgang Denk
2011-10-17 20:48 ` Ilya Yanok
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=201106181621.46436.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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