From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 18 Jan 2016 23:24:57 +0100 Subject: [Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected In-Reply-To: <877fj64jhn.fsf@dell.be.48ers.dk> References: <1425230275-127768-1-git-send-email-kaszak@gmail.com> <20160109172908.GA3444@free.fr> <87y4bn6y5s.fsf@dell.be.48ers.dk> <20160118214704.GA3380@free.fr> <20160118230345.52b8f054@free-electrons.com> <877fj64jhn.fsf@dell.be.48ers.dk> Message-ID: <20160118232457.472dc051@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Peter, On Mon, 18 Jan 2016 23:21:08 +0100, Peter Korsgaard wrote: > > I also don't like the way the patch is implemented, but I think the > > problem raised by this patch is real. Sometimes people have kernel > > sources that contain some custom kernel headers needed for their > > userspace libraries/applications, and we have no mechanism to allow > > them to use their custom kernel source for the linux-headers package, > > which is a bit annoying. > > Yeah, true. It does require that these custom header files are really > exported (so they get installed by headers_install) which in my > experience is not always the case. > > What I have told people to do in the past instead is to either copy the > needed definitions into their user space code or add > -I$(LINUX_DIR)/include (if they build their kernel in Buildroot) like > E.G. xdriver_xf86-video-imx does it. Yes, I know there are ways around it. But it does seem weird to many users that the "linux" package provides some many possibilities for fetching/patching the kernel, and still the linux-headers package downloads a completely different kernel version, with less possibilities of using a custom version. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com