From: Scott Wood <scottwood@freescale.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.com, Timur Tabi <timur@freescale.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: Build failure on treeboot-walnut.cg
Date: Thu, 11 Oct 2007 15:02:37 -0500 [thread overview]
Message-ID: <20071011200237.GB4247@loki.buserror.net> (raw)
In-Reply-To: <18189.27251.48582.614106@cargo.ozlabs.ibm.com>
On Thu, Oct 11, 2007 at 10:12:35AM +1000, Paul Mackerras wrote:
> Timur Tabi writes:
>
> > Is this a new policy? Modules in the kernel are not built unless you want
> > them. Even in arch/powerpc/platforms, only the specific platform file I'm
> > targeting is built. So I don't really understand why you claim it's normal
> > for platform-specific files to be built, regardless of the actual platform.
>
> The wrapper script is intended to be a standalone tool which is
> independent of the kernel configuration, and can be used separately
> from the kernel build process.
Is it ever actually used that way? I wonder if this "intent" is worth the
pain...
-Scott
next prev parent reply other threads:[~2007-10-11 20:02 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 [this message]
2007-10-09 16:06 ` Scott Wood
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=20071011200237.GB4247@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.