Optional target: sys-cluster/heartbeat-3.0.3 Since it's going to be depreciated in future releases you can either keyword it or just add sys-cluster/pacemaker[heartbeat] to use.mask Thanks!
Background: pacemaker cluster manager can use either heartbeat-3.x or corosync+openais as communication layer. Upstream and major distros are all going on corosync, heartbeat-3.x development is actually stopped and kept just for bugfixes. See http://www.clusterlabs.org/wiki/FAQ#Should_I_Run_Pacemaker_on_Heartbeat_or_Coroysnc.3F for details. cluster herd is supporting both on x86/amd64, and I'm testing the whole cluster infrastructure on HPPA using corosync (same setup as the two amd64 clusters I manage at work); I'm not gonna test or use heartbeat-3.x on any platform since it's already a thing of the past. pacemaker and its deps (USE=ais) build just fine on HPPA and I can get corosync start and talking between the nodes. openais currently has some problems and that prevents all the other stuff (like pacemaker) to run correctly. I'm looking into the issue, it could well be related to my testing environment (linux-vserver guests). Will report back here as soon as I have some (hopefully good) news.
Marked ~hppa.