Avik, Your debuild looks good. I have never seen this error.
Is there a reason you need a packaged kernel? In general dealing with packaged kernels is more difficult than just doing a simple crosscompile. The instructions of PackageYourOwnKernel are for those who need a packaged kernel for inclusion in for example hwpacks. If you are adding some new functionality to the linaro kernel then just use Nicolas' current kernel which right now is git://git.linaro.org/kernel/linux-linaro-2.6.36.git. Once you have the new functionality working then send patches or a pull request to Nicolas. He will pull them into his tree. Then I will pull them into the packaged natty kernel tree. John On Fri, Dec 3, 2010 at 11:48 AM, Nicolas Pitre <nicolas.pi...@linaro.org> wrote: > On Fri, 3 Dec 2010, Avik Sil wrote: > >> I tried to build with the fix using debuild. It seems it now compiles the >> kernel correctly but fails at later stage when debuild performs some >> post-build checks. The build output can be found here: >> http://pastebin.com/kB5kpTMS >> >> I use 'debuild -eCROSS_COMPILE=arm-linux-gnueabi- -b -aarmel' command >> for building. >> >> Nicolas, can you please tell me the reason for this error? I consulted the >> steps given in https://wiki.linaro.org/PackageYourOwnKernel > > Sorry, I've never used debuild myself. > > Do you get the same issue without the lttng patches merged, i.e. when > using the standard linaro-2.6.36 tree? > > > Nicolas > _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
