<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to compile a kernel for Ubuntu Jaunty</title>
	<atom:link href="http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/</link>
	<description>Just my thoughts about things</description>
	<lastBuildDate>Wed, 10 Mar 2010 23:17:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ritesh Sinha</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-4192</link>
		<dc:creator>Ritesh Sinha</dc:creator>
		<pubDate>Fri, 11 Sep 2009 09:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-4192</guid>
		<description>Thank you Peter for the very detailed article on compiling kernels. However without sounding like a git myself, I noticed that after I had cloned the Jaunty tree, the debian directory doesn&#039;t contain any of the files that require editing. Instead, these files are under the debian.master directory. 

Are the two directories fundamentally different or do I edit the files in the debian.master directory and proceed? I tried doing that (editing the files under debian.master instead of debian) but the build stage fails (Error: couldn&#039;t find debian/control).

Its probably a stupid mistake on my part but I&#039;d be really grateful if you could point out where I&#039;ve screwed up. Again, thanks for taking the time to write the detailed instructions.</description>
		<content:encoded><![CDATA[<p>Thank you Peter for the very detailed article on compiling kernels. However without sounding like a git myself, I noticed that after I had cloned the Jaunty tree, the debian directory doesn&#8217;t contain any of the files that require editing. Instead, these files are under the debian.master directory. </p>
<p>Are the two directories fundamentally different or do I edit the files in the debian.master directory and proceed? I tried doing that (editing the files under debian.master instead of debian) but the build stage fails (Error: couldn&#8217;t find debian/control).</p>
<p>Its probably a stupid mistake on my part but I&#8217;d be really grateful if you could point out where I&#8217;ve screwed up. Again, thanks for taking the time to write the detailed instructions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shyam</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3716</link>
		<dc:creator>Shyam</dc:creator>
		<pubDate>Thu, 30 Jul 2009 08:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3716</guid>
		<description>Guys, first thanks for your help. I finally nailed it, its even easier to compile in karmic. See my blog for procedure to do it in karmic.</description>
		<content:encoded><![CDATA[<p>Guys, first thanks for your help. I finally nailed it, its even easier to compile in karmic. See my blog for procedure to do it in karmic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbernardo</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3715</link>
		<dc:creator>jbernardo</dc:creator>
		<pubDate>Thu, 30 Jul 2009 06:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3715</guid>
		<description>You can&#039;t cross compile, that is build a kernel for one architecture while running a different architecture, using this method (or at least I have not found how to do it). To build a amd64 kernel, you have to be running a amd64 distribution or a amd64 chroot. I stumbled on the same problem trying to build a lpia kernel, and solved it by creating a chroot. Just google for &quot;chroot ubuntu&quot; and you&#039;ll find quite a few suggestions.

If someone has a easier solution towards cross compiling a kernel....</description>
		<content:encoded><![CDATA[<p>You can&#8217;t cross compile, that is build a kernel for one architecture while running a different architecture, using this method (or at least I have not found how to do it). To build a amd64 kernel, you have to be running a amd64 distribution or a amd64 chroot. I stumbled on the same problem trying to build a lpia kernel, and solved it by creating a chroot. Just google for &#8220;chroot ubuntu&#8221; and you&#8217;ll find quite a few suggestions.</p>
<p>If someone has a easier solution towards cross compiling a kernel&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alonso</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3712</link>
		<dc:creator>Alonso</dc:creator>
		<pubDate>Wed, 29 Jul 2009 20:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3712</guid>
		<description>hi, 

I have done everithing changing i386 with amd64, but when I try to compile the kernel I get:

# CONCURRENCY_LEVEL=2 NOEXTRAS=1 skipabi=true skipmodule=true fakeroot debian/rules binary-core2
make: *** No rule to make target `binary-core2&#039;.  Stop.


Any ideas?

Thanks</description>
		<content:encoded><![CDATA[<p>hi, </p>
<p>I have done everithing changing i386 with amd64, but when I try to compile the kernel I get:</p>
<p># CONCURRENCY_LEVEL=2 NOEXTRAS=1 skipabi=true skipmodule=true fakeroot debian/rules binary-core2<br />
make: *** No rule to make target `binary-core2&#8242;.  Stop.</p>
<p>Any ideas?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbernardo</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3709</link>
		<dc:creator>jbernardo</dc:creator>
		<pubDate>Wed, 29 Jul 2009 13:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3709</guid>
		<description>The hardest part for me in building for karmic (even more thansetting up the chroot to build a lpia kernel) was the config files. You need to copy your config to (assuming the same values as the examples above) debian/config/i386/config.flavour.core2

Then you need to run &quot;debian/scripts/misc/kernelconfig editconfig&quot; which will do a menuconfig on all config files, allowing you to change yours or any of them, and finally will merge common stuff to the common scripts (debian/config/config.common.ubuntu &amp; debian/config/config.common.ports, besides the ones already mentioned) and split the separate stuff into each flavour file.

PS: I am typing the config.* names as I recall them, since I am not on my pc right now.</description>
		<content:encoded><![CDATA[<p>The hardest part for me in building for karmic (even more thansetting up the chroot to build a lpia kernel) was the config files. You need to copy your config to (assuming the same values as the examples above) debian/config/i386/config.flavour.core2</p>
<p>Then you need to run &#8220;debian/scripts/misc/kernelconfig editconfig&#8221; which will do a menuconfig on all config files, allowing you to change yours or any of them, and finally will merge common stuff to the common scripts (debian/config/config.common.ubuntu &amp; debian/config/config.common.ports, besides the ones already mentioned) and split the separate stuff into each flavour file.</p>
<p>PS: I am typing the config.* names as I recall them, since I am not on my pc right now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3708</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 29 Jul 2009 13:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3708</guid>
		<description>I don&#039;t have karmic installed, don&#039;t have a spare computer for it. I think if you would follow the suggestions given here about Karmic, you should be able to pull it off.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t have karmic installed, don&#8217;t have a spare computer for it. I think if you would follow the suggestions given here about Karmic, you should be able to pull it off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shyam</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3707</link>
		<dc:creator>Shyam</dc:creator>
		<pubDate>Wed, 29 Jul 2009 12:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3707</guid>
		<description>Is there a full description of karmic files or a guide to compile kernel 2.6.31-X for karmic. I am trying to create new flavour for xps laptops, huge config changes, but I think i need to split config before start the compile.</description>
		<content:encoded><![CDATA[<p>Is there a full description of karmic files or a guide to compile kernel 2.6.31-X for karmic. I am trying to create new flavour for xps laptops, huge config changes, but I think i need to split config before start the compile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbernardo</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3578</link>
		<dc:creator>jbernardo</dc:creator>
		<pubDate>Sun, 19 Jul 2009 18:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3578</guid>
		<description>For karmic, things change a little. You no longer edit control, but create a vars.core2 inside debian/control.d (I just copied vars.generic, removed the amd64 architecture entry and changed the description), and run &quot;debian/rules debian/control&quot; to generate the control file before building the kernel. Also, as Gunnar writes above, the config files now have a config.common.arch and a config.flavour.&quot;flavour&quot;.</description>
		<content:encoded><![CDATA[<p>For karmic, things change a little. You no longer edit control, but create a vars.core2 inside debian/control.d (I just copied vars.generic, removed the amd64 architecture entry and changed the description), and run &#8220;debian/rules debian/control&#8221; to generate the control file before building the kernel. Also, as Gunnar writes above, the config files now have a config.common.arch and a config.flavour.&#8221;flavour&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvaro</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3554</link>
		<dc:creator>Alvaro</dc:creator>
		<pubDate>Thu, 16 Jul 2009 04:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3554</guid>
		<description>Hi Peter

Out of all the &quot;compiling kernel guides&quot; on the net, you are the only one playing with:

    * debian/scripts/misc/getabis
    * debian/rules.d/i386.mk
    * debian/control.stub
    * debian/control

where can I get official info about those files, why no one else modifies those files?
I&#039;m wondering this now cause I never had problem compiling the kernel for debian or ubuntu and never had modified those files either. But now I&#039;m compiling a kernel for a small distro based in debian and I get the following error:

dpkg-gencontrol -DArchitecture=i386 -isp -plinux-image-2.6.26-geode-v1 -P/usr/src/linux/debian/linux-image-2.6.26-geode-v1/
dpkg-gencontrol: error: package linux-image-2.6.26-geode-v1 not in control info
make[2]: *** [debian/stamp/binary/linux-image-2.6.26-geode-v1] Error 255
make[2]: Leaving directory `/usr/src/linux-source-2.6.26-voyage&#039;
make[1]: *** [debian/stamp/binary/pre-linux-image-2.6.26-geode-v1] Error 2
make[1]: Leaving directory `/usr/src/linux-source-2.6.26-voyage&#039;
make: *** [kernel_image] Error 2

It seems that I need to set up those files in a similar way as you do...

can you suggest me something ?

Thanks</description>
		<content:encoded><![CDATA[<p>Hi Peter</p>
<p>Out of all the &#8220;compiling kernel guides&#8221; on the net, you are the only one playing with:</p>
<p>    * debian/scripts/misc/getabis<br />
    * debian/rules.d/i386.mk<br />
    * debian/control.stub<br />
    * debian/control</p>
<p>where can I get official info about those files, why no one else modifies those files?<br />
I&#8217;m wondering this now cause I never had problem compiling the kernel for debian or ubuntu and never had modified those files either. But now I&#8217;m compiling a kernel for a small distro based in debian and I get the following error:</p>
<p>dpkg-gencontrol -DArchitecture=i386 -isp -plinux-image-2.6.26-geode-v1 -P/usr/src/linux/debian/linux-image-2.6.26-geode-v1/<br />
dpkg-gencontrol: error: package linux-image-2.6.26-geode-v1 not in control info<br />
make[2]: *** [debian/stamp/binary/linux-image-2.6.26-geode-v1] Error 255<br />
make[2]: Leaving directory `/usr/src/linux-source-2.6.26-voyage&#8217;<br />
make[1]: *** [debian/stamp/binary/pre-linux-image-2.6.26-geode-v1] Error 2<br />
make[1]: Leaving directory `/usr/src/linux-source-2.6.26-voyage&#8217;<br />
make: *** [kernel_image] Error 2</p>
<p>It seems that I need to set up those files in a similar way as you do&#8230;</p>
<p>can you suggest me something ?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://blog.avirtualhome.com/2009/04/29/how-to-compile-a-kernel-for-ubuntu-jaunty/#comment-3483</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sat, 04 Jul 2009 22:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.avirtualhome.com/?p=385#comment-3483</guid>
		<description>Sounds like you are in the wrong directory.
If you have everything in : /d1/kernel/jaunty that where you execute the command.</description>
		<content:encoded><![CDATA[<p>Sounds like you are in the wrong directory.<br />
If you have everything in : /d1/kernel/jaunty that where you execute the command.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
