linux-kernel - Re: [Announce] Checkpoint-restore tool v0.4

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:	Fri, 22 Feb 2013 10:01:19 +0100 (CET)
From:	Jan Engelhardt <jengelh@...i.de>
To:	Pavel Emelyanov <xemul@...allels.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Containers <containers@...ts.linux-foundation.org>,
	CRIU <criu@...nvz.org>
Subject: Re: [Announce] Checkpoint-restore tool v0.4


On Wednesday 2013-02-20 12:18, Pavel Emelyanov wrote:
>
>As was planned, the v0.4 of C/R tools is out, right after the Linux v3.8.
>
>The most valuable thing in this release, is that all the kernel patches
>we had are now merged, and thus what crtools-v0.4 can do will work on
>the upstream kernel (properly configured)!

I have trouble compiling that.


$ + make -j10 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' V=1
gcc -M -MT arch/x86/crtools.d -MT arch/x86/crtools.o -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g   arch/x86/crtools.c -o arch/x86/crtools.d
arch/x86/crtools.c:5:21: fatal error: asm/fpu.h: No such file or directory

fpu.h does not exist in /usr/include, nor does it exist in $linux/arch/x86/
or $linux/include. Apparently it does exist in crtools, but there are no
more flags pointing to crtools/include/. Which probably means you should
place mandatory CFLAGS not in CFLAGS, but your own variable.
--
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/