shortly following the stable release of valgrind 2.2.0, the helpful tool callgrind (formerly known as calltree) has been updated to support the latest version of valgrind. I'll soon post an ebuild that works fine for me. Reproducible: Always Steps to Reproduce:
Created attachment 38941 [details] callgrind-0.9.9.ebuild note that I changed the name of the ebuild to callgrind (like the name of the tool itself changed) and I would suggest putting it into a new category dev-util/callgrind I added a blocker on dev-util/calltree (the old name/version of this tool)
another side note on this. no matter how you get this latest version into portage tree, it's important to see it in there soon, cause calltree-0.9.7 crashes when used with valgrind-2.2.0. so the new version is important. btw... calltree-0.9.7-r1 should reject to install when valgrind-2.2.0 is inplace (and maybe valgrind 2.2.0 should also refuse to install when an older calltree version is still in place)
Created attachment 38942 [details] calltree-0.9.7-r1.ebuild.diff a tiny patch for the calltree-0.9.7-r1 ebuild to better show up it supports _ONLY_ valgrind-2.1.2
sorry for bumping this one, but I've got no reactions so far... when using valgrind 2.2.0 calltree-0.9.7-r1 just crashes - so this updated version is really needed
committed the changes.
If this is going to be the new package, perhaps kdesdk should not try to pull in calltree and depend on callgrind now. Currently I have callgrind installed, but kdesdk keeps trying to pull in calltree and downgrade valgrind. Don't know if I should post this here and hope for the bug to be reopened or create a new one.
Reopened bug for HaLCy0n in #gentoo-bugs.
I think we might either use some virtual package that is provided by calltree and callgrind on which me make kdesdk depend to get past this problem... or make kdesdk depend on callgrind (but this way forcing everyone away from older (stable?) calltree versions an have them use callgrind)
ok, here is my solution for this problem, tested it myself and works fine for me... 1) make all versions of calltree and callgrind PROVIDE="virtual/calltree" 2) make kcachegrind and >=kdesdk-3.2.0 DEPEND on "virtual/calltree" instead of "dev-util/calltree" 3) make "virtual/calltree" default to "dev-util/calltree" in the needed profile's virtuals files 4) if you had callgrind/calltree installed emerge it again or manually register the virtual it provides
I don't have callgrind emerged, but this is what "emerge -upDv world" gives wrt valgrind-2.2.0: ----------------- # emerge -upDv world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild N ] net-fs/samba-3.0.7-r1 -acl +cups -debug -doc -kerberos +ldap -mysql -oav +pam -postgres +python +readline (-selinux) -xml +xml2 0 kB [ebuild UD] dev-util/valgrind-2.1.2 [2.2.0] +X -debug 0 kB [ebuild U ] app-office/openoffice-ximian-1.3.5 [1.3.4] -debug -gnome -java +kde 2,776 kB Total size of downloads: 2,776 kB ------------------- However, trying to emerge valgrind on its own: ------------------- # emerge -upDv valgrind These are the packages that I would merge, in order: Calculating dependencies ...done! Total size of downloads: 0 kB ------------------- or: ------------------- # emerge -pv valgrind These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-util/valgrind-2.2.0 +X -debug 0 kB Total size of downloads: 0 kB ------------------- Checking callgrind gives me this: ------------------- # emerge -upDv callgrind These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] dev-util/calltree (from pkg dev-util/callgrind-0.9.9) [ebuild U ] sys-apps/sed-4.1.2 [4.0.9] -build -debug +nls -static 749 kB [ebuild U ] sys-devel/gcc-3.4.2-r2 [3.4.1-r3] -bootstrap -build -debug -f77 -gcj -gtk -hardened -n32 -n64 +nls -nomultilib -objc -static (-uclibc) 33 kB [ebuild N ] dev-util/callgrind-0.9.9 176 kB Total size of downloads: 958 kB ------------------- Regards, MickKi
should all be fixed now
Sorry, but I am not so sure :-/ This is what I'm getting now: -------------------------- # emerge -upDv world These are the packages that I would merge, in order: Calculating world dependencies ...done! [blocks B ] dev-util/calltree (from pkg dev-util/callgrind-0.9.9) [ebuild U ] media-libs/taglib-1.3 [1.2] -debug 716 kB [ebuild N ] dev-util/callgrind-0.9.9 176 kB [ebuild UD] dev-util/valgrind-2.1.2 [2.2.0] +X -debug 0 kB [ebuild U ] net-dialup/ppp-2.4.2-r3 [2.4.2-r2] -activefilter -atm -debug -ipv6 +pam 756 kB [ebuild U ] app-office/openoffice-ximian-1.3.5 [1.3.4] -debug -gnome -java +kde 2,776 kB [ebuild U ] sys-apps/hotplug-20040923 [20040920] 43 kB Total size of downloads: 4,469 kB # emerge -upDv dev-util/valgrind These are the packages that I would merge, in order: Calculating dependencies ...done! Total size of downloads: 0 kB --------------------------------------- So, calltree is blocked due to callgrind-0.9.9, while valgrind-2.2.0 wants to downgrade to 2.1.2, but hold on, no it doesn't when I am trying to update it on its own!!! OK, with my limited knowledge this is too confusing . . . These are some dependencies: --------------------------------------- # emerge -upDvt valgrind These are the packages that I would merge, in reverse order: Calculating dependencies ...done! Total size of downloads: 0 kB --------------------------------------- Can this be correct?! Finally: --------------------------------------- # emerge -upDvt calltree These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [nomerge ] dev-util/calltree-0.9.7-r1 [ebuild UD] dev-util/valgrind-2.1.2 [2.2.0] +X -debug 0 kB Total size of downloads: 0 kB # emerge -upDvt callgrind These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [blocks B ] dev-util/calltree (from pkg dev-util/callgrind-0.9.9) [ebuild N ] dev-util/callgrind-0.9.9 176 kB [nomerge ] sys-apps/man-1.5m-r1 -debug +nls Total size of downloads: 176 kB --------------------------------------- All my flags are as per previous emerge info. Please feel free to PM me if you need more info.
Oops! Just read a bit more . . . (time passes). Unmerged calltree and problem solved ;-) Perhaps I was expecting calltree to be unmerged by callgrind - or an error/warning message telling me to do so? Which you might argue is what the blocking message was all about (sigh). Anyway, please ignore previous report. Just finished compiling it :o)
