Bug#610653: ITP: dmtcp -- Checkpoint/Restart functionality for Linux processes
ah -- I think I've forgotten:
* now it builds with optimization suppressed in many places, e.g.
gcc -m32 -Wa,--32 -DHIGHEST_VA=0xffffe000 -g -O2 -O0 -g -c -o mtcp_check_vdso.o mtcp_check_vdso.c
is that required? if not then it better be 'regulated' by noopt option,
usually done with a snippet like
CFLAGS = -Wall -g
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
CFLAGS += -O0
else
CFLAGS += -O2
endif
I see in ./mtcp/Makefile:
,---
| #Currently sometimes can't link libmtcp.so without CFLAGS=-O0
| CFLAGS += -O0 -g
`---
is it the case still?
* (perspective TODO) -- it would be nice to have dmtcp-dbg package containing
debug symbols, so if bug discovered, users could simply install it to provide
meaningful context. implementation is easy -- just add such package to
debian/control and instruct dh_strip to dump symbols into that package:
dh_strip --dbg-package=dmtcp-dbg
in your debian/rules
Cheers
On Tue, 25 Jan 2011, Gene Cooperman wrote:
> Hi Yaroslav,
> Thanks very much for mentoring us on the Debian package. We greatly
> appreciate this. Here are two finer points: If Kapil already discussed
> them with you, then you can ignore this.
--
=------------------------------------------------------------------=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
Reply to: