|
From: Stefan K. <en...@ho...> - 2009-12-29 17:06:51
|
Am 29.12.2009 17:19, schrieb Bart Van Assche: > On Tue, Dec 29, 2009 at 11:53 AM, Konstantin Serebryany > <kon...@gm...> wrote: >> First question: >> Valgrind installation contains include files, which makes me think that it is possible to build valgrind tools w/o having the valgrind sources. >> However, with the current version of valgrind, it does dot work: include/valgrind/pub_tool_basics.h includes "config.h", which is not a part of valgrind installation. >> Can that be fixed? > > The header file "config.h" is included because the configure script > figures out whether or not the selected compiler supports > __builtin_expect() (HAVE_BUILTIN_EXPECT). Since gcc supports > __builtin_expect() since at least gcc 3.0, and since we only support > gcc 3.2 and above, it's probably safe to remove the #ifdef > HAVE_BUILTIN_EXPECT and #include "config.h". If such case arises in the future again, its better to have a valgrind_onfig.h.in and let configure generate it. That generated file can be installed with the other includes. Atleast I have encountered this scheme in other software. Stefan > >> Third question: >> Few of the valgrind public headers are not C++-able. >> Can that be fixed? > > Should be fixed through r10970 and r10971. By the way, r10970 builds > fine on Darwin and x86-64 but not on PPC. > > Bart. > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |