> Cc: to the OpenMPI list as the oftdump clash might be of interest
> elsewhere.
>
>> I attach a patch, but it doesn't work and I don't see where the
>> error lies now. It may be that I'm doing something stupid.
>> It produces working OpenMPI-1.3.4 package on Dragonfly though.
>
> Ok, I'll try and merge it in to the working stuff we have here.
> I, obviously, just #ifdef'd for NetBSD as that is all I have to
> try stuff out against.

No need for that actually, we can do it later.
I was using Dragonfly as platform where it works out of box.

>> (What conflict do you observe with pkgsrc-wip package by the way?)
>>
>
> That was detailed in another email but basically the Open Trace Format
> that the Vampire Trace (VT) stuff is looking to install tries to install:
>
> ${LOCALBASE}/bin/otfdump
>
> and that binary is already installed there as part of another
> package.
>
> You can get around this for a NetBSD OpenMPI deployment by adding this
> patch to the PkgSrc Makefile which just removes the VT toolkit:
>
>
> 26a27
>> CONFIGURE_ARGS+= --enable-contrib-no-build=vt
>
> I have no idea how NetBSD go about resolving such clashes in the long
> term though?

I've disabled it the same way for this time, my local package differs
from what's in wip: