From: Scott Wood <scottwood@freescale.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.com, Timur Tabi <timur@freescale.com>
Subject: Re: Build failure on treeboot-walnut.cg
Date: Tue, 9 Oct 2007 11:06:45 -0500 [thread overview]
Message-ID: <20071009160645.GA4304@loki.buserror.net> (raw)
In-Reply-To: <20071009030729.GI12499@localhost.localdomain>
On Tue, Oct 09, 2007 at 01:07:29PM +1000, David Gibson wrote:
> On Mon, Oct 08, 2007 at 04:33:24PM -0500, Timur Tabi wrote:
> > Question: I'm building a kernel for the 8610. Why is treeboot-walnut.c
> > being compiled at all?
>
> Policy. Compiling everything means build bugs - like this one - can
> be found by everybody, not just those building for the specific
> obscure platform.
Of course, it also introduces bugs that wouldn't have been an issue if we
didn't try to build everything with the same toolchain. :-P
I'm also somewhat worried what it'll do to build time as platforms
accumulate.
-Scott
next prev parent reply other threads:[~2007-10-09 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 22:46 Build failure on treeboot-walnut.c Grant Likely
2007-09-26 0:15 ` Josh Boyer
2007-10-08 21:33 ` Timur Tabi
2007-10-09 3:07 ` Build failure on treeboot-walnut.cg David Gibson
2007-10-09 16:06 ` Timur Tabi
2007-10-09 18:52 ` Josh Boyer
2007-10-09 19:14 ` Kumar Gala
2007-10-10 2:35 ` David Gibson
2007-10-11 0:12 ` Paul Mackerras
2007-10-11 20:02 ` Scott Wood
2007-10-09 16:06 ` Scott Wood [this message]
2007-10-10 2:35 ` David Gibson
2007-10-09 4:00 ` Build failure on treeboot-walnut.c Grant Likely
2007-10-09 13:30 ` Kumar Gala
2007-10-09 14:44 ` Timur Tabi
2007-10-09 14:51 ` Geert Uytterhoeven
2007-10-09 14:51 ` Kumar Gala
2007-10-09 14:54 ` Timur Tabi
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=20071009160645.GA4304@loki.buserror.net \
--to=scottwood@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.com \
--cc=paulus@samba.org \
--cc=timur@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).