From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: Possible rdma-core header conflict Date: Thu, 24 Aug 2017 09:27:13 -0600 Message-ID: <20170824152713.GB23110@obsidianresearch.com> References: <20170821120310.GL1724@mtr-leonro.local> <20170821155729.GC4401@obsidianresearch.com> <20170822064704.GR1724@mtr-leonro.local> <20170824105007.GH1724@mtr-leonro.local> <20170824122328.GJ1724@mtr-leonro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170824122328.GJ1724@mtr-leonro.local> Sender: linux-kbuild-owner@vger.kernel.org To: Leon Romanovsky Cc: Yigal Korman , mmarek@suse.com, linux-kbuild@vger.kernel.org, dhowells@redhat.com, Linux RDMA Mailing List List-Id: linux-rdma@vger.kernel.org On Thu, Aug 24, 2017 at 03:23:28PM +0300, Leon Romanovsky wrote: > For the development, I use ability of rdma-core to run everything in > place and I don't install anything. I compile with build.sh supplied > in rdma-core and adjust Makefiles to point to build/lib|include directories > without need to install. For development you can also tell rdma-core to refer to the kernel source tree directly and it will immediately use those kernel header for RDMA. No need to install things and wreck your distro. # -DKERNEL_DIR='.../linux' (default '') # If set use the kernel UAPI headers from this kernel source # tree. Jason