lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 31 Mar 2008 20:00:22 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Stefan Hellermann <stefan@...2masters.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: make O=dir fails with current git

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ