From: Sam Ravnborg <sam@ravnborg.org>
To: Stefan Hellermann <stefan@the2masters.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make O=dir fails with current git
Date: Mon, 31 Mar 2008 20:00:22 +0200 [thread overview]
Message-ID: <20080331180022.GA4833@uranus.ravnborg.org> (raw)
In-Reply-To: <47EE8829.10409@the2masters.de>
On Sat, Mar 29, 2008 at 07:19:21PM +0100, Stefan Hellermann wrote:
> Hi,
>
> I'm using "make O=machinename" for building different kernels from one tree. About 15 days
> ago it was okay, with current git it fails:
> $ make O=client1
> scripts/kconfig/conf -s arch/x86/Kconfig
> Using /srv/devel/kernel as source for kernel
> /srv/devel/kernel is not clean, please run 'make mrproper'
> in the '/srv/devel/kernel' directory.
> make[1]: *** [prepare3] Error 1
> make: *** [sub-make] Error 2
>
> running "make mrproper" (without O=dir) doesn't help.
> I've not changed anything, I only made a "git-pull".
> Now I'm at home, tried "mkdir test; make O=test defconfig all" with current git-head, it
> doesn't work too.
I tried to reproduce this here without luck.
The tests performed by kbuild to dertermine if the
source directory is clean are very basic.
If the file .config exist or the directory
include/config exists then the source tree is considered clean.
Otherwise you get the above message.
Can you please try to run: make mrproper
and then manually check if the .config file
or the include/config directory exists.
If they exists after make mrproper then
check your permissions.
In any case let me know the result.
Sam
next prev parent reply other threads:[~2008-03-31 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 18:19 make O=dir fails with current git Stefan Hellermann
2008-03-31 18:00 ` Sam Ravnborg [this message]
2008-03-31 18:26 ` Stefan Hellermann
2008-03-31 18:42 ` Sam Ravnborg
2008-04-03 16:51 ` Pavel Machek
2008-03-31 18:34 ` Randy Dunlap
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=20080331180022.GA4833@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@the2masters.de \
/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