public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: re librdmacm-devel dependency on librdmacm
Date: Wed, 2 Feb 2011 12:42:02 +0200	[thread overview]
Message-ID: <4D4934FA.8070905@voltaire.com> (raw)

Hi Sean,

I just realized the librdmacm-devel (version 1.0.8-5.el5 is installed on 
the system I hit that) is dependent on librdmacm, and wasn't sure if its 
a bug or a feature... the dependency is created through 
/usr/lib64/librdmacm.so which is soft link to the obj file installed by 
librdmacm.

Or.

> [root@celery ~]# rpm -qR librdmacm-devel
> libibverbs-devel >= 1.1
> librdmacm = 1.0.8-5.el5
> librdmacm.so.1()(64bit)
> rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> [root@celery ~]# rpm -ql librdmacm-devel | grep -v man
> /usr/include/rdma
> /usr/include/rdma/rdma_cma.h
> /usr/include/rdma/rdma_cma_abi.h
> /usr/lib64/librdmacm.so
> [root@celery ~]# ls -l /usr/lib64/librdmacm*
> lrwxrwxrwx 1 root root    18 Feb  2 12:22 /usr/lib64/librdmacm.so -> 
> librdmacm.so.1.0.0
> lrwxrwxrwx 1 root root    18 Feb  2 12:22 /usr/lib64/librdmacm.so.1 -> 
> librdmacm.so.1.0.0
> -rwxr-xr-x 1 root root 21376 Jun 22  2009 /usr/lib64/librdmacm.so.1.0.0
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2011-02-02 10:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 10:42 Or Gerlitz [this message]
     [not found] ` <4D4934FA.8070905-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2011-02-02 15:24   ` re librdmacm-devel dependency on librdmacm Hefty, Sean
     [not found]     ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25CC0C1C2C-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-02-02 15:43       ` Or Gerlitz
     [not found]         ` <4D497BA7.9070701-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2011-02-02 15:55           ` Hefty, Sean
     [not found]             ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25CC0C1C85-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-02-02 16:54               ` Greg Kerr
2011-02-02 19:30               ` Or Gerlitz
2011-02-02 22:40   ` Steven Dake
     [not found]     ` <4D49DD4E.4070904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-02-02 22:47       ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D4934FA.8070905@voltaire.com \
    --to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox