From: Cyrill Gorcunov <gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Jan Engelhardt <jengelh-9+2X+4sQBs8@public.gmane.org>
Cc: CRIU <criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.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-F2ai0iW9ZajH9RFtKMg/Ng@public.gmane.org>
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.
WARNING: multiple messages have this Message-ID (diff)
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.
next prev parent reply other threads:[~2013-02-22 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 11:18 [Announce] Checkpoint-restore tool v0.4 Pavel Emelyanov
2013-02-20 11:18 ` Pavel Emelyanov
[not found] ` <5124B107.1040302-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-02-22 9:01 ` Jan Engelhardt
2013-02-22 9:01 ` Jan Engelhardt
[not found] ` <alpine.LNX.2.01.1302220955160.1805-F2ai0iW9ZajH9RFtKMg/Ng@public.gmane.org>
2013-02-22 9:13 ` Cyrill Gorcunov [this message]
2013-02-22 9:13 ` [CRIU] " Cyrill Gorcunov
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-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=jengelh-9+2X+4sQBs8@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.