On Thu, Jan 26, 2017 at 11:54:53PM +0200, Yishai Hadas wrote: > Correct, the link will be explicitly by the application at compile time so > that the exported symbols will be resolved. Okay, then you just need to make that possible. > >Somehow libmlx needs to be in the standard ld.so search path, and > >available for linking via gcc, as well as continuing to be a plugin.. > >The best choice might be to put it in /usr/lib/../libmlx5.so.1 and > >symlink that file to /usr/lib/../libibverbs/libmlx5-rdmav2.so > > You are pointing on same usage as done for libibverbs which has the symlink, > correct ? libibverbs has a symlink for a different purpose. > Alternatively, application can use the linker flags as part of its > Makefile to find the shared library location, isn't it ? No, that would require applications to hardwire /usr/lib/.../libibverbs/libmlx5-rdmav2.so as a path. Do not want that. Make it so gcc -libverbs_dv_mlx5 foo.c Is all that is required. 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
