From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: powerpc: Fix make rules for dtc
Date: Mon, 9 Oct 2006 16:21:31 +0200 [thread overview]
Message-ID: <811124BA-A99B-46B9-9A16-4111D937468E@kernel.crashing.org> (raw)
In-Reply-To: <20061009002945.GA2259@localhost.localdomain>
>>> clean-files := $(zlib) $(zlibheader) $(zliblinuxheader) \
>>> - $(obj)/empty.c
>>> + $(obj)/empty.c *.dtb
>>
>> If this wildcard works at all, it will still do the wrong thing:
>> deleting all .dtb files (even the ones that the Makefile cannot
>> create again, e.g., the user put them in the tree manually) is
>> at best not very polite.
>
> It certainly works at all
My problem with it is the := which might be expanded at the wrong
time. Or maybe that won't glob the *.dtb yet, who knows. It's
not obviously "working" either way.
> (the preceding $(obj)/empty.c, however, is
> wrong, I've sent a separate patch for that). One could say the same
> thing for *.o in clean targets,
Yes, and that's a very well-known problem.
> though I guess adding .dtb files is
> rather more likely. However, I can't seen an obvious way of
> generating a list of the re-creatable dtbs, without an explicit
> listing of every file in arch/powerpc/boot/dts which sounds like a bit
> of a pain. Suggestions?
You shouldn't clean _all_ dtb's that you could build, only the dtb's
that you _did_ build. You already have a rule for what dtb's to
build I assume; just copy the logic from there.
Segher
next prev parent reply other threads:[~2006-10-09 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 3:37 powerpc: Fix make rules for dtc David Gibson
2006-10-04 3:41 ` powerpc: Fix clean target for empty.c David Gibson
2006-10-05 17:58 ` powerpc: Fix make rules for dtc Segher Boessenkool
2006-10-09 0:29 ` David Gibson
2006-10-09 14:21 ` Segher Boessenkool [this message]
2006-10-10 0:23 ` David Gibson
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=811124BA-A99B-46B9-9A16-4111D937468E@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).