Installing KCachegrind in order to profile output from ruby-prof turned out to be quite a time consuming task.
This was all performed on an iMac with a 2.16 GHz Intel Core 2 Duo CPU and 4GB 667 MHz DDR2 SDRAM.
The initial command:
sudo port install kcachegrind
ran for several hours only to fail with :
checking for XPROTO... configure: error: Package requirements (xproto >= 7.0.13) were not met: Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11
I manually installed the correct version of xorg-xproto:
sudo port deactivate xorg-xproto # deactivates version 7.0.11_1 sudo port install xorg-xproto # installs version 7.0.14_1
Restarted the KCachegrind install:
sudo port install kcachegrind
Then waited again.
The next error encountered:
---> Activating xorg-renderproto @0.9.3_0 Error: Target org.macports.activate returned: Image error: /opt/local/include/X11/extensions/render.h is being used by the active render port. Please deactivate this port first, or use the -f flag to force the activation.
I did what the error message suggested:
sudo port -f activate xorg-renderproto
It looks as though some other install had installed files
/opt/local/include/X11/extensions/render.h /opt/local/include/X11/extensions/renderproto.h
the install process copied the old files to a tmp directory. A quick diff of the files showed that the installed files were the newer files.
Restarted the install of kcachegrind:
sudo port install kcachegrind
The install continued for several more hours. kdelibs3 taking 2 hours.
When everything was finally installed I do have a working version of kcachegrind running.
In total the install ran for approximately 8 hours.
I needed to use kcachegrind a few weeks ago to profile ruby-prof but the tought of spending all that time compiling it put me off. I instead spent an extra hour or two going though the output with my eye balls.
I hope someone packages it up in a .app bundle like gimp or inkscape.
May 8, 2009 at 10:42 pm
My experience:
8 core MacPro, with macports configured for parallel builds = 1 hour total build time :)
My macports did not know about the newer version of xorg-xproto, but a _sudo port selfupdate_ then a _sudo port upgrade xorg-xproto_ took care of business.
Kdelibs3 failed to build the first time through. I ran _sudo port install kdelibs3_ twice from the command line and it succeeded the second time. I suspect bugs in their makefile and/or they should not be opting in for parallel building.
May 20, 2009 at 5:49 pm