> > So I have a dev system setup with everything installed from the distro in /usr. > > I have my rdma-core git tree. I change libcxgb4 to fix a bug. I want to test > > it. I install it to /usr/local and add /etc/ld.so.conf.d/usrlocal.conf. But > > that still doesn't work because ldconfig still finds libcxgb4 in /usr/lib64 > > first... > > Apply this patch: > > https://github.com/jgunthorpe/rdma- > plumbing/commit/64ed4fd30a2157bdaf0a8f7f1b04d2dad02c1b8f > > It hardwires the search path into libverbs and libverbs will look into > the place it was installed before searching the system library > path. That will eliminate the problem you mentioned above. > > Further, after that patch is applied you can do a rough imitation of > 'run-in-place' like this: > > $ cmake .. -DVERBS_PROVIDER_DIR:PATH=`pwd`/lib - > DSYSCONF_INSTALL_DIR:PATH=/etc > And how do I build this after the cmake? > (untested) That hardwires the build directory into libibverbs, so it > will try to load all drivers from there first. > > Then use > > $ export LD_LIBRARY_PATH=`pwd`/lib > > And all verbs using programs started from that shell will use the full > new library set and the new providers without having to do make > install at all. > > I plan to automate this basic approach for 'run in place', please let > me know if it works for you and makes sense. > > Jason > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
