From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?= Date: Mon, 17 Dec 2012 16:57:39 +0100 (CET) Subject: [Buildroot] [PATCH] imx-lib: new package In-Reply-To: <50CF3F4D.1030100@mind.be> References: <1355752131-31966-1-git-send-email-arnout@mind.be> <50CF3F4D.1030100@mind.be> Message-ID: <2112128925.1003709.1355759859440.JavaMail.root@advansee.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Arnout Vandecappelle, On Monday, December 17, 2012 4:50:37 PM, Arnout Vandecappelle wrote: > On 17/12/12 14:48, Arnout Vandecappelle (Essensium/Mind) wrote: > > +IMX_LIB_INCLUDE = \ > > + -I$(LINUX_DIR)/drivers/mxc/security/rng/include \ > > + -I$(LINUX_DIR)/drivers/mxc/security/sahara2/include \ > > + -I$(LINUX_DIR)/include > > Actually, I wonder if this is the right thing to do... This is a > userspace library that requires a platform-specific linux/xxx.h. For > an > external toolchain, these headers don't exist in > $(STAGING_DIR)/usr/include/linux > > Directly using $(LINUX_DIR)/include means that the headers are not > patched for userspace. For those platform-specific headers that's > probably not a problem, but it's not good for e.g. linux/types.h. > > An easy workaround is to use -idirafter instead of -I. However, > perhaps it's an even better idea to do 'make headers_install' as part > of > the normal linux build process, so that packages depending on those > headers can use the patched version. But then again, is it a good > idea to > replace the toolchain's kernel headers with a new set of kernel > headers? > > Any advice is welcome! FYI, I've successfully built the 11.09.01 version under BuildRoot without the "-I$(LINUX_DIR)/include", and the issue that you mention is only for this folder. I had to make a patch to make the headers install work, but that should not be related. Can you try with your package? Best regards, Beno?t