From: Dag W. <da...@wi...> - 2003-04-27 18:04:13
|
Hi, I'm building valgrind for several versions of the Red Hat distribution.=20 You can find these packages at: http://dag.wieers.com/packages/valgrind/ Or have them installed automatically using apt as described on: http://dag.wieers.com/apt/ The RH9 package is build on a clean RH9 by doing 'unset CFLAGS' as=20 described in RH BugZilla #88846. make was not updated. I also included a small C program that would check if NPTL threading was=20 supported (at runtime). But I superseded that with using getconf directly= .=20 (This works on all distributions and is much cleaner.) Using getconf was advised on a mailinglist somewhere (I can't remember=20 where exactly I read that.) However I have the source of the small C=20 program still in my SPEC file for educational purposes.) It would be nice though if valgrind could check for itself if NPTL=20 threading is supported at loadtime ? Or at least take over my changes to=20 coregrind/valgrind.in so that it is check in runtime (instead of checking= =20 at compile-time) You can do this by doing: perl -pi.orig -e 's|^nptl_threading=3D.*$|nptl_threading=3D"$(if getconf = GNU_LIBPTHREAD_VERSION &>/dev/null; then echo "yes"; else echo "no"; fi)"= |' coregrind/valgrind.in PS These packages still have a problem with some private GLIBC symbols=20 that are in the dependencies of the package. I can't seem to fix this by=20 doing: %define __find_provides() /usr/lib/rpm/find-provides %* | grep -v '^libp= thread.so' %define __find_requires() /usr/lib/rpm/find-requires %* | grep -v 'libc.= so.6(GLIBC_PRIVATE)' So unless I find a clean way of doing this, you might have to install wit= h=20 --nodeps on some RH's (RH80 and RH73 afaik). PS2 I'm not subscribed, please put me in CC if you have any remarks. Kind regards, -- dag wieers, da...@wi..., http://dag.wieers.com/ -- =ABAny errors in spelling, tact or fact are transmission errors=BB |