Quoting Oren Laadan ([email protected]):
>
> Serge E. Hallyn wrote:
> >
> > Yes, it'd be useful. BTW it also would be useful to have mktree/
> > restart auto-detect such error strings and report them.
> >
>
> 'ckptinfo -e' should already do this, but sure, we can add a switch
Oh, ha, I wouldn't know, bc ckptinfo has never compiled for me, and
I'd never yet cared to beat it into compiling.
Looks like it will work for me if I do
export KERNELHDR=/usr/include
in my shell before compiling, and use the following patch:
diff --git a/Makefile b/Makefile
index afff3f5..f7bd93b 100644
--- a/Makefile
+++ b/Makefile
@@ -48,7 +48,7 @@ mktree: CFLAGS += -D__REENTRANT -pthread
ckptinfo_types.o: ckptinfo_types.c
@echo $(CC) -c $(CFLAGS) $<
- @$(CC) -c $(CFLAGS) $<
+ @$(CC) -D__GLIBC__=2 -c $(CFLAGS) $<
ckptinfo_types.c: $(CKPT_HEADERS) ckptinfo.py
@echo cat $(CKPT_HEADERS) | ./ckptinfo.py > ckptinfo_types.c
> to 'restart' to check it too. An dyes, in the kernel definitely.
>
> Oren.
_______________________________________________
Containers mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/containers
_______________________________________________
Devel mailing list
[email protected]
https://openvz.org/mailman/listinfo/devel
