|
From: Julian S. <js...@ac...> - 2007-01-04 03:43:54
|
The reason vex is built statically is that valgrind is linked statically and without glibc. Allowing glibc and dynamic linking to be part of valgrind is a recipe for stability and portability problems and as a result of those concerns, about 2 years ago there was a transition to the current static linking and no use of libc support. J On Thursday 04 January 2007 03:39, Stephen Torri wrote: > I am working on getting VEX to build with the automake, autoconf and > libtool GNU tools. Right now I am coming down to a issue of linking. > When I compile a tool, like memcheck, I am getting issues with linking > memcheck with a shared library version of VEX. I did not see a reason > why VEX should only be a static library. Who is the main point of > contact on the valgrind build system? > > Stephen > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |