if you did not configure with --disable-dlopen, you need to make install from opal/mca/btl/If if not, you need make install from your top builddir
you can mpirun --mca btl_base_verbose 100 ... to see if your btl was found and did not somehow disqualify itself (for example because it's priority is zero) Cheers, Gilles On Thursday, March 17, 2016, 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. >
