Paul sent me some additional info off-list, and I fixed the issue.

PR's filed for v1.10 and v2.x.


> On Aug 19, 2015, at 5:09 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
> wrote:
> 
> On Aug 19, 2015, at 5:01 PM, Todd Kordenbrock <thkgc...@gmail.com> 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 you are -- and those are there because of --enable-static 
> --disable-shared.  So: all is good there.
> 
>> As far as the 3 occurrences of the Portals4 path in that linker line, it 
>> breaks down as one -L and two -rpath.  I think the -rpath shows up twice 
>> because Portals4 depends on libev.so which is installed in the same place as 
>> libportals.so and you get one -rpath for each lib.  I'll see if that can be 
>> deduped.
> 
> K.  Not a huge deal, but would be nice to fix up.
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2015/08/17765.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Reply via email to