Paul --
I'm unable to replicate this behavior.
But I also don't have the portals libraries.
Can you send your configure output, config.log, and full "make V=1" output?
Thanks.
> On Aug 15, 2015, at 1:17 AM, Paul Hargrove wrote:
>
> On a Linux/x86-64 system I have configure with
> --enable-d
Jeff,
I have determined that the problem persists without the --with-portals4.
I will send the requested log files and output off-list.
-Paul
On Wed, Aug 19, 2015 at 12:01 PM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> Paul --
>
> I'm unable to replicate this behavior.
>
> But I als
Thanks.
It *is* a little odd, though, that the portals flags are showing up in the OFI
MTL linker line -- they probably shouldn't be. Todd K. is looking into it.
> On Aug 19, 2015, at 4:10 PM, Paul Hargrove wrote:
>
> Jeff,
>
> I have determined that the problem persists without the --with-
Jeff,
The linker error that Paul posted isn't an OFI MTL specific linker line.
It is the linker line for otfmerge-mpi from VampirTrace package. Portals4
just shows up as an external library the same as OFI or torque.
As far as the 3 occurrences of the Portals4 path in that linker line, it
breaks
On Aug 19, 2015, at 5:01 PM, Todd Kordenbrock wrote:
>
> Jeff,
>
> The linker error that Paul posted isn't an OFI MTL specific linker line. It
> is the linker line for otfmerge-mpi from VampirTrace package. Portals4 just
> shows up as an external library the same as OFI or torque.
Ah, right
