linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: ppcdev <linuxppc-dev@ozlabs.org>, Sam Ravnborg <sam@ravnborg.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: Merge dtc
Date: Fri, 19 Oct 2007 00:56:41 -0500	[thread overview]
Message-ID: <1b5c57d93e45d94d007b543ea5e2de02@bga.com> (raw)
In-Reply-To: <20071019014510.GD30283@localhost.localdomain>

On Oct 18, 2007, at 8:45 PM, David Gibson wrote:
> On Thu, Oct 18, 2007 at 09:59:26PM +0200, Sam Ravnborg wrote:
>> On Thu, Oct 18, 2007 at 12:49:54PM -0500, Milton Miller wrote:
>>> On Tue Oct 16 15:02:17 EST 2007, David Gibson wrote:
>>>
>>>> This very large patch incorporates a copy of dtc into the kernel
>>>> source, in arch/powerpc/boot/dtc-src.  This means that dtc is no
>>>> longer an external dependency to build kernels with configurations
>>>> which need a dtb file.
>
>> As Milton already pointed out you should build dtc in the
>> dtc directory (why the -src prefix??).
>
> The -src suffix is only there because I'm not building in the
> directory - we can't have both a dtc binary and a dtc directory in
> arch/powerpc/boot.

So run the dtc binary stored in the sub directory.  Thats what we do 
elsewhere.

> Ok, so how do I build in the subdirectory?  I was going to do that,
> but couldn't for the life of me figure out how.

Documentation/kbuild/makefiles.txt  6.4 boot images:

         "$(Q)$(MAKE) $(build)=<dir>" is the recommended way to invoke
         make in a subdirectory.

Section 4 Host Program Support is also relavent, and mentions $(always).


>> And the dtc specific Makefile looks like something from
>> the late 80'. Please drop all these ALLUPPERCASE variables
>> and accept a little bit of redundancy.
>
> Hrm... I'm pretty dubious about this.  Practically every Makefile in
> the universe, *except* Kbuild uses uppercase for most variables.
> Makefile.dtc is imported verbatim from the standalone dtc package, and
> is supposed to have the minimal information about what needs to be
> built to import into Makefiles that actually know how to build things.
>
>> Then mere humans may be able to read the Makefile.
>
> Says a maintainer of Kbuild, about my tiny and not-very-complex
> Makefile fragment... um, ok...

overley complex calls to override source, conditional rules based on 
shipped files?  Its not a trivial fragment.

milton

  reply	other threads:[~2007-10-19  5:56 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 17:49 Merge dtc Milton Miller
2007-10-18 19:59 ` Sam Ravnborg
2007-10-19  1:45   ` David Gibson
2007-10-19  5:56     ` Milton Miller [this message]
2007-10-19  6:55       ` David Gibson
2007-10-19  7:07         ` Sam Ravnborg
2007-10-19  7:10           ` David Gibson
2007-10-19 18:42             ` Sam Ravnborg
2007-10-31  2:45               ` David Gibson
2007-11-08 13:59                 ` Jon Loeliger
2007-10-19  1:30 ` David Gibson
2007-10-19  5:34   ` Milton Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-10-16  5:02 David Gibson
2007-10-16  5:08 ` Kumar Gala
2007-10-16  5:18   ` David Gibson
2007-10-16  5:39   ` Paul Mackerras
2007-10-16  5:50     ` Kumar Gala
2007-10-16  6:01       ` Benjamin Herrenschmidt
2007-10-16  6:23         ` Kumar Gala
2007-10-16 10:53         ` Josh Boyer
2007-10-17 19:59       ` Timur Tabi
2007-10-17 20:12         ` Josh Boyer
2007-10-17 20:31           ` Grant Likely
2007-10-17 21:42         ` Linas Vepstas
2007-10-17 21:51           ` Jon Loeliger
2007-10-16  6:00     ` Benjamin Herrenschmidt
2007-10-16  6:24       ` Kumar Gala
2007-10-16 13:17 ` Grant Likely
2007-10-16 13:41   ` Kumar Gala
2007-10-17  5:22   ` David Gibson
2007-10-17 13:15     ` Grant Likely
2007-10-17 16:22       ` Stephen Neuendorffer
2007-12-04  1:59 ` David Woodhouse
2007-12-04  3:10   ` David Gibson
2007-12-04 17:22     ` David Woodhouse
2007-12-04 13:25   ` Jon Loeliger
2007-12-04 15:26     ` Josh Boyer
2007-12-04 16:04       ` Kumar Gala
2007-12-04 22:12         ` David Gibson
2007-12-04 16:08     ` Scott Wood
2007-12-04 22:21   ` Paul Mackerras
2007-12-04 22:33     ` David Woodhouse
2007-12-05  0:54       ` David Woodhouse
2007-12-05  1:49         ` Josh Boyer
2007-12-05  1:09       ` Paul Mackerras
2007-12-04 22:34     ` Josh Boyer
2007-12-05  2:22       ` Paul Mackerras
2007-12-05  2:26         ` Josh Boyer
2007-12-05  4:00           ` Josh Boyer
2007-12-05  4:37             ` Olof Johansson

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=1b5c57d93e45d94d007b543ea5e2de02@bga.com \
    --to=miltonm@bga.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sam@ravnborg.org \
    /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).