From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Sender: had2006@gmail.com In-Reply-To: <20150313140403.GD1497@hermes.click-hack.org> References: <54F97594.2060605@xenomai.org> <54F97E05.8010107@xenomai.org> <54FF64AF.5000300@xenomai.org> <5500A3DD.2070306@xenomai.org> <8dc6116b7b5868d884c9f8c3e3de3c84.squirrel@xenomai.org> <20150313140403.GD1497@hermes.click-hack.org> Date: Fri, 13 Mar 2015 16:27:32 +0000 Message-ID: From: Helder Daniel Content-Type: text/plain; charset=UTF-8 Subject: Re: [Xenomai] Fwd: Error boilerplate/wrappers.h no found trying to compile RTDM module on 3.x-rc3 cobalt List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: "Xenomai@xenomai.org" On 13 March 2015 at 14:04, Gilles Chanteperdrix < gilles.chanteperdrix@xenomai.org> wrote: > On Fri, Mar 13, 2015 at 01:50:07PM +0000, Helder Daniel wrote: > > Just for a sanity check I installed Xenomai 2.6.4 > > and created kernel-headers-3.14.17 patched with ipipe-core > > Well, once again: if the kernel-headers package contains symbolic > link to xenomai sources, then you have to keep xenomai sources (or > the reduced xenomai-kernel-sources package) around. The Xenomai sources are at: /usr/src/xenomai-3.0-rc3 > How did you > generate the kernel, with prepare-kernel.sh ? > yes: /usr/src/xenomai-3.0-rc3/scripts/prepare-kernel.sh --linux=/usr/src/linux-3.16 --ipipe=/usr/src/xenomai-3.0-rc3/kernel/cobalt/arch/x86/patches/ipipe-core-3.16-x86-3.patch > Does the kernel-header package contain the .config? Yes. > > > > > them make /lib/modules/3.14.17-ipipe/build points to the kernel-headers > and > > not the full kernel source. > > Well, it is silly to touch that build symbolic link: > 1- the debian packages are supposed to handle that > Yes > 2- when building a kernel module you are supposed to pass the path > to kernel source as a parameter to the make -C command. So, simply > passing the path to the kernel headers location should avoid having > to touch the symbolic link. as documented in Documentation/kbuild/modules.txt in the kernel sources. > Yes, I could do that I was just testing. Instead I changed the symbolic link to test if with a standard Makefile, the problem is just info that is missing in the headers and are in the source tree. (But I could test the same modifying the path in the Makefile...)