Hi all Anyone willing to help? :-)
I now have a follow up question: I was trying to figure this out myself by taking the backtrace from the BTLs that do work, and found that, since most of the internal functions are not exported, the backtraces contain just the addresses which are not all that helpful (this is even after building with --enable-debug.) This is going back to a question that I myself asked recently, and I am now finding out the answer the hard way! Is there any way that all the internal functions, not explicitly declared 'static' can be made visible? Thanks Durga Life is complex. It has real and imaginary parts. On Wed, Mar 16, 2016 at 12:52 PM, dpchoudh . <dpcho...@gmail.com> wrote: > Hello all > > Sorry about asking too many 101 level question, but here is another one: > > I have a BTL layer code, called 'lf' that is ready for unit testing; it > compiles with the OMPI tool chain (by doing a ./configure; make from the > top level directory) and have the basic data transport calls implemented. > > How do I 'hook up' the BTL to the OMPI call chain? > > If I do the following: > mpirin -np 2 --hostfile ~/hostfile -mca btl lf,self ./NPmpi > > it fails to run and the gist of the failure is that it does not even > attempt connecting with the 'lf' BTL (the error says: 'BTLs attempted: > self') > > The 'lf' NIC, and RDMA capable card, also has a TCP/IP interface and > replacing 'lf' with 'tcp' in the above command *does* work. > > Thanks in advance > Durga > > Life is complex. It has real and imaginary parts. >
