public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Yigal Korman <yigal-/8YdC2HfS5554TAoqtyWWQ@public.gmane.org>,
	Linux RDMA Mailing List
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Possible rdma-core header conflict
Date: Mon, 21 Aug 2017 09:57:29 -0600	[thread overview]
Message-ID: <20170821155729.GC4401@obsidianresearch.com> (raw)
In-Reply-To: <20170821120310.GL1724-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>

On Mon, Aug 21, 2017 at 03:03:10PM +0300, Leon Romanovsky wrote:
> On Mon, Aug 21, 2017 at 12:24:14PM +0300, Yigal Korman wrote:
> > Hi,
> > Has anyone noticed that installing rdma-core (or older
> > librdmacm-devel) package and then installing kernel headers manually
> > (make headers_install) removes the librdmacm headers?
> > I actually see it in the make output:
> >
> > make INSTALL_HDR_PATH=/usr headers_install
> >   CHK     include/generated/uapi/linux/version.h
> >   REMOVE  rdma_cma_abi.h rdma_verbs.h rdma_cma.h rsocket.h
> >
> > Am I doing something wrong?
> > Sounds like the kernel rdma headers and librdmacm headers shouldn't
> > sit in the same directory...
> 
> It looks like this behavior (removal of header files) was from the beginning of git era.
> ➜  linux-rdma git:(rdma-next) ✗ git co -b tmp v2.6.34.8
> ➜  linux-rdma git:(tmp) ✗ cp ~/src/rdma-core/librdmacm/rdma_verbs.h /tmp/h/include/rdma/ && make INSTALL_HDR_PATH=/tmp/h headers_install | grep REMOVE
>   REMOVE  rdma_verbs.h

The user space files have also been sharing the directory with the
kernel files since the start.. Not sure why, but I don't think we can
change it now.

Maybe someone can patch the kernel to exempt rdma/ from the removal
process?

Jason
--
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

  parent reply	other threads:[~2017-08-21 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  9:24 Possible rdma-core header conflict Yigal Korman
     [not found] ` <CACTTzNa3EzABie9=h2X-ONBefyaoWE1+RAT-T+uxJVvVij15Rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-21 12:03   ` Leon Romanovsky
     [not found]     ` <20170821120310.GL1724-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-08-21 15:57       ` Jason Gunthorpe [this message]
     [not found]         ` <20170821155729.GC4401-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-08-22  6:08           ` Yigal Korman
2017-08-22  6:47             ` Leon Romanovsky
2017-08-24 10:50               ` Leon Romanovsky
2017-08-24 11:28                 ` Yigal Korman
2017-08-24 12:23                   ` Leon Romanovsky
2017-08-24 15:27                     ` Jason Gunthorpe
     [not found]                       ` <20170824152713.GB23110-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-08-24 15:34                         ` Leon Romanovsky

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=20170821155729.GC4401@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yigal-/8YdC2HfS5554TAoqtyWWQ@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