From: David Howells <dhowells@redhat.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: dhowells@redhat.com, Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: CONFIG_MODULE_SIG breaks out-of-tree modules in modpost.
Date: Mon, 15 Oct 2012 13:19:07 +0100 [thread overview]
Message-ID: <17290.1350303547@warthog.procyon.org.uk> (raw)
In-Reply-To: <6862.1350090285@turing-police.cc.vt.edu>
Valdis Kletnieks <Valdis.Kletnieks@vt.edu> wrote:
> /bin/sh: -c: line 0: syntax error near unexpected token `;'
> /bin/sh: -c: line 0: `set -e; ; echo 'cmd_/usr/src/valdis/NVIDIA-Linux-x86_64-304.51/kernel/nvidia.ko := ' > /usr/src/valdis/NVIDIA-Linux-x86_64-304.51/kernel/.nvidia.ko.cmd'
I would guess that this is from Kbuild.include's 'if_changed' macro:
if_changed = $(if $(strip $(any-prereq) $(arg-check)), \
@set -e; \
$(echo-cmd) $(cmd_$(1)); \
echo 'cmd_$@ := $(make-cmd)' > $(dot-target).cmd)
unless nvidia.ko has its own build rules.
It looks like either $(call if_changed) got invoked with no arguments or
$(cmd_$(1)) didn't exist.
Could you find out what $(1) was by adding a bit:
if_changed = $(if $(strip $(any-prereq) $(arg-check)), \
$(info XXXX $(1)) \
@set -e; \
$(echo-cmd) $(cmd_$(1)); \
echo 'cmd_$@ := $(make-cmd)' > $(dot-target).cmd)
You should see a line looking something like:
XXX link_o_target
emitted by make just before it the error occurs.
David
next prev parent reply other threads:[~2012-10-15 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 1:04 Valdis Kletnieks
2012-10-15 12:19 ` David Howells [this message]
2012-10-18 10:22 ` Wei Yongjun
2012-10-18 10:57 ` Stefan Knoblich
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=17290.1350303547@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.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
all inboxes | Powered by JetHome®