From: Timur Tabi <timur@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Paul Mackerras <paulus@samba.org>,
ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Someone broke my allmodconfig build
Date: Mon, 23 Jul 2007 10:47:07 -0500 [thread overview]
Message-ID: <46A4CD7B.7070001@freescale.com> (raw)
In-Reply-To: <fa686aa40707230807k450ff82dv11201ca3a4ce4c9b@mail.gmail.com>
Grant Likely wrote:
> On 7/23/07, Timur Tabi <timur@freescale.com> wrote:
>> Stephen Rothwell wrote:
>>
>> >> Hmmm, we should be shipping .dtb files with the tree, so people don't
>> >> have to have dtc installed.
>> >
>> > Unless, of course, we ship dtc ...
>>
>> I like that idea.
>>
>> I don't know much about the kernel build process, but is it normal to
>> ship C files and have kbuild build them and then use the executables
>> to build the rest of the kernel?
>
> That's how Kconfig is built.
Then it shouldn't be too hard to refactor the dtc build environment to make it
Kbuild-compatible, and then Paul can pull from Jon's dtc repo whenever it gets updated.
Jon, what do you think?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-07-23 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 14:12 Someone broke my allmodconfig build Stephen Rothwell
2007-07-22 0:37 ` Paul Mackerras
2007-07-22 1:53 ` Stephen Rothwell
2007-07-23 13:15 ` Timur Tabi
2007-07-23 15:07 ` Grant Likely
2007-07-23 15:17 ` Josh Boyer
2007-07-23 15:47 ` Timur Tabi [this message]
2007-07-22 2:04 ` Josh Boyer
2007-07-23 1:43 ` David Gibson
2007-07-23 15:24 ` Mark A. Greer
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=46A4CD7B.7070001@freescale.com \
--to=timur@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).