linux-kernel - Re: 2.6.23.git build error

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]

Message-Id: <1192260909.7369.20.camel@Homer.simpson.net>
Date:	Sat, 13 Oct 2007 09:35:09 +0200
From:	Mike Galbraith <efault@....de>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Giacomo Catenazzi <cate@...ian.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.23.git build error

On Sat, 2007-10-13 at 09:16 +0200, Sam Ravnborg wrote:

> Pulled 2.6.23 tree and did a build
> Added latest -linus on top of it.
> Did a new build (x86_64).
> 
> 
> As expected it failed due to wrong asm symlink but nothing
> like the error Mike posted.
> So I'm a bit puzzeled here.
> 
> I anyone can explain how to reproduce it I will chase it
> but otherwise it will be left as a "consequence of
> the x86 merge".

What I did was to pull, then diff against my working tree (/me=SCM
weenie;) for review as usual, and then apply that diff to working tree
and make oldconfig as usual.  That left me with the same failure this
morning, despite the file being verified present in the git tree.  I
then used git-archive --format=tar | (cd work_tree;tar -xvf -).  That
spewed chunks when I tried to build it even though diff said the trees
were identical.  After make mrproper and restoring my saved .config, all
was peachy.

Methinks dontdiff bit me.

	-Mike

-
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/