From: Michal Marek <mmarek@suse.cz>
To: Rabin Vincent <rabin@rab.in>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: make KBUILD_NOCMDDEP=1 handle empty built-in.o
Date: Thu, 12 May 2011 15:33:56 +0200 [thread overview]
Message-ID: <20110512133356.GI13293@sepie.suse.cz> (raw)
In-Reply-To: <BANLkTimLre+UY1fY6+HXEsJicyh_oMnWdA@mail.gmail.com>
On Wed, May 11, 2011 at 11:00:01PM +0530, Rabin Vincent wrote:
> On Tue, Apr 26, 2011 at 22:36, Rabin Vincent <rabin@rab.in> wrote:
> > Fix building with KBUILD_NOCMDDEP=1, which currently does not work
> > because it does not build built-in.o with no dependencies:
> >
> > LD fs/notify/built-in.o
> > ld: cannot find fs/notify/dnotify/built-in.o: No such file or directory
> > ld: cannot find fs/notify/inotify/built-in.o: No such file or directory
> > ld: cannot find fs/notify/fanotify/built-in.o: No such file or directory
> >
> > Signed-off-by: Rabin Vincent <rabin@rab.in>
>
> Any comments on this patch? I found KBUILD_NOCMDDEP useful
> when hunting down a bug that appeared only in a certain compiler
> version. Used it to build some files using one compiler and the rest
> using the other. It would be nice if it worked out of the box; it will
> after this patch.
OK, so you have a use case for it. I was about to ask if it wouldn't be
easier to drop this feature instead :).
>
> > ---
> > scripts/Kbuild.include | 4 ++++
> > 1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
> > index ed2773e..fd31781 100644
> > --- a/scripts/Kbuild.include
> > +++ b/scripts/Kbuild.include
> > @@ -187,6 +187,10 @@ ifneq ($(KBUILD_NOCMDDEP),1)
> > # User may override this check using make KBUILD_NOCMDDEP=1
> > arg-check = $(strip $(filter-out $(cmd_$(1)), $(cmd_$@)) \
> > $(filter-out $(cmd_$@), $(cmd_$(1))) )
> > +else
> > +# Ensure that files with no dependencies are built.
> > +built-check = $(filter $(origin cmd_$@), undefined)
> > +arg-check = $(if $(strip $(obj-y)),,$(built-check))
> > endif
I'm not sure if this is the rigt way to fix it. Kbuild.include should
not care about obj-*. The problem is that arg-check is always empty with
KBUILD_NOCMDDEP and if there are no other dependencies, the target will
not be created, right? IMO we only need to make sure that during the
first make run, arg-check always expands to non-empty, even with
KBUILD_NOCMDDEP. So we can drop the $(obj-y) test and do it like this
(untested), can't we?
diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
index c034dd7..be39cd1 100644
--- a/scripts/Kbuild.include
+++ b/scripts/Kbuild.include
@@ -197,6 +197,8 @@ ifneq ($(KBUILD_NOCMDDEP),1)
# User may override this check using make KBUILD_NOCMDDEP=1
arg-check = $(strip $(filter-out $(cmd_$(1)), $(cmd_$@)) \
$(filter-out $(cmd_$@), $(cmd_$(1))) )
+else
+arg-check = $(if $(strip $(cmd_$@)),,1)
endif
# >'< substitution is for echo to work,
while at it, we should also add KBUILD_NOCMDDEP to
Documentation/kbuild/kbuild.txt.
Michal
next prev parent reply other threads:[~2011-05-12 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:06 Rabin Vincent
2011-05-11 17:30 ` Rabin Vincent
2011-05-12 13:33 ` Michal Marek [this message]
2011-05-15 17:37 ` Rabin Vincent
2011-05-16 14:44 ` Michal Marek
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=20110512133356.GI13293@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
/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
all inboxes | Powered by JetHome®