public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Pavel Emelyanov <xemul@parallels.com>, CRIU <criu@openvz.org>,
	Linux Containers <containers@lists.linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [CRIU] [Announce] Checkpoint-restore tool v0.4
Date: Fri, 22 Feb 2013 13:13:26 +0400	[thread overview]
Message-ID: <20130222091326.GA17499@moon> (raw)
In-Reply-To: <alpine.LNX.2.01.1302220955160.1805@nerf07.vanv.qr>

On Fri, Feb 22, 2013 at 10:01:19AM +0100, Jan Engelhardt wrote:
> 
> 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.

Thanks for report, i'll fix that.

      reply	other threads:[~2013-02-22  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 11:18 [Announce] Checkpoint-restore tool v0.4 Pavel Emelyanov
2013-02-22  9:01 ` Jan Engelhardt
2013-02-22  9:13   ` Cyrill Gorcunov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130222091326.GA17499@moon \
    --to=gorcunov@openvz.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=criu@openvz.org \
    --cc=jengelh@inai.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xemul@parallels.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox