Re: rdma-core packaging and multilib

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 15, 2017 at 12:34:37PM -0400, Doug Ledford wrote:
 
> That's not entirely true.  The man page specifically says the path in
> the man page is an example, so it need not match the arch in use, it can
> simply be one or the other with no substitution.  For the provider lib
> path, it's in a comment, so again it would be possible to use proper
> verbage to express that it is a sample and not use substitution.  We
> might even be able to do something like:
> 
> # Modern distros commonly use either /usr/lib or /usr/lib64 for the
> # default _libpath.  Substitute the correct value below before
> # uncommenting
> # provider_lib_path _libpath/ibacm

Debian derived uses /usr/lib/x86_64-linux-gnu

I think change the man page like:

       To add a provider to the ibacm core service, the provider must

       1. be implemented as a shared library;

       2. be installed under the configured directory, (see the output
       of ib_acme -D . -O)

       3  export a function provider_query() that returns a pointer to its provider info
          and version info.

And something similar for the etc file? The RH spec file produces the
etc file by running the ib_acme command, so it should sedscript in the
right text..

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



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux