From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kbuild: allow code re-use across different directories
Date: Wed, 28 Sep 2011 23:42:27 +0200 [thread overview]
Message-ID: <20110928214227.GA17628@sepie.suse.cz> (raw)
In-Reply-To: <1315974254-17345-1-git-send-email-lacombar@gmail.com>
On Wed, Sep 14, 2011 at 12:24:14AM -0400, Arnaud Lacombe wrote:
> Modify Kbuild to allow direct code re-use in multiple directory
> without having to go through a copy. Technically, Kbuild would use by
> default the VPATH feature
I now found that the patch breaks headers_install and firmware_install
when using O=
$ mkdir build
$ make O=build defconfig
...
$ make O=build headers_install
CHK include/linux/version.h
UPD include/linux/version.h
HOSTCC scripts/unifdef
make[3]: *** No rule to make target `scripts/headers_install.pl', needed by `/labs/mmarek/linux-2.6/build/usr/include/asm-generic/.install'. Stop.
make[2]: *** [asm-generic] Error 2
make[1]: *** [headers_install] Error 2
make: *** [sub-make] Error 2
$ make O=build firmware_install
GEN /labs/mmarek/linux-2.6/build/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
make[2]: *** No rule to make target `firmware/e100/d101m_ucode.bin', needed by `/lib/firmware/e100/d101m_ucode.bin'. Stop.
make[1]: *** [firmware_install] Error 2
make: *** [sub-make] Error 2
Michal
next prev parent reply other threads:[~2011-09-28 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 4:24 [PATCH] Kbuild: allow code re-use across different directories Arnaud Lacombe
2011-09-25 20:13 ` Arnaud Lacombe
2011-09-28 21:42 ` Michal Marek [this message]
2011-09-28 22:20 ` Arnaud Lacombe
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=20110928214227.GA17628@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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