linux-kernel - Re: make O=dir fails with current git

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] [day] [month] [year] [list]

Date:	Thu, 3 Apr 2008 18:51:19 +0200
From:	Pavel Machek <pavel@....cz>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Stefan Hellermann <stefan@...2masters.de>,
	linux-kernel@...r.kernel.org
Subject: Re: make O=dir fails with current git

Hi!

> > >> 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.
> > 
> > Hi, damn, it's that easy!
> > It was the .config file, I added (as root) a symlink to dir/.config to let some other
> > application check if some Kernel-options are set, then the permissions of this symlink
> > prevented make mrproper from removing it.
> > 
> > For what purpose is this check?
> The O= build will use the wrong files if the source tree is not clean.
> There are several special cases which goes wrong under the wrong circumstances
> and therefore this consistency check.

Actually, I keep hitting this all the time. I run make in source tree,
and before I realize my mistake, it creates include/config... which I
have to remove manually before I can use make O=...

Could it perhaps remove include/config when .config does not exist?

Or create include/config only after writting .config?

	(answering 1000 questions takes time, its easy to hit ^c
	there....)
						Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/