Callgrind uses runtime instrumentation via the Valgrind framework for its
cache simulation and call tracing. This way, even shared libraries and
dynamically opened plugins can be profiled. The data files generated by
Callgrind can be loaded into KCachegrind for browsing the performance results.
But there is also a command line tool in the Callgrind package to get ASCII
reports from Callgrind data files without the need to use KCachegrind.
WWW: http://kcachegrind.sourceforge.net
===> The following configuration options are available for callgrind-0.9.8:
VALGRIND_SNAPSHOT=off (default) "Depend on snapshot version of valgrind"
===> Use 'make config' to modify these settings
- remove broken/expired ports@ ports
Approved by: portmgr (miwi)
audio/ccaudio||2010-01-18|Has expired: has been broken for 4 months
audio/py-libmpdclient||2010-01-18|Has expired: has been broken for 3 months
chinese/gbk2uni||2010-01-18|Has expired: has been broken for 6 months
chinese/iiimf-le-xcin||2010-01-18|Has expired: has been broken for 3 months
devel/adabindx||2010-01-18|Has expired: has been broken for 3 months
devel/agide||2010-01-18|Has expired: has been broken for 6 months
devel/asis||2010-01-18|Has expired: has been broken for 3 months
devel/callgrind||2010-01-18|Has expired: Included in devel/valgrind
devel/florist||2010-01-18|Has expired: has been broken for 3 months
editors/xml2rfc-xxe||2010-01-18|Has expired: has been broken for 4 months
graphics/gephex||2010-01-18|Has expired: has been broken for 3 months
(Only the first 15 lines of the commit message are shown above )
Use IGNORE instead of BROKEN.
Pointed out by: danfe
Porters' handbook chapter to be re-read by me: 17.19 (Marking a port
BROKEN, FORBIDDEN, or otherwise not installable)
Approved by: arved (implicit)