linux-kernel - Re: build breakage -- paravirt_{alloc,free}

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, 12 Jan 2009 12:35:20 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	linux-kernel@...r.kernel.org,
	Jaswinder Singh Rajput <jaswinderrajput@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: build breakage -- paravirt_{alloc,free}_ldt

On Mon, 12 Jan 2009, Ingo Molnar wrote:

> > Puzzled. On one system, I still get this build error even after make 
> > mrpoper (I use this machine to build kernel routinely, so it certainly 
> > didn't happen a few days ago).
> > But I just tried on different system, and there is builds flawlessly. 
> > It's gcc 4.3.1 vs 4.3.2. I will check a little bit more.
> beyond mrproper you might want to try 'git checkout HEAD . -f' as well, to 
> get a forced checkout of the current working tree. Should there be any 
> corruption in any of the source code files this will get rid of it.

I did a completely fresh clone instead, and it works since that ... 
strange. Anyway sorry for alse alarm.

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