About as simple as it gets

[pika_pika]

I'm trying to create my first kernel, and all has gone fairly well up until now.

I downloaded 2.4.3.tar.gz, and the associated patche(s) off of kernel.org for my mandrake 7.2.

I'm not sure if when I've run the linux/scripts/patches if it is already patched. It just spits back to me that 'Current kernel version is 2.4.3'. I mean did I even have to download the 2.4.3 patch? Anyhow, after extracting the tar to /usr/src/linux I did what the site said and make mrproper (what does this run? Is mrproper another script?). After that I was going to just make menuconfig which I would expect is safer for me at this point then just make config. Anyhow, this is the message I received: make: *** No rule to make target 'config'. Stop. What am I missing here? Both the site on the readme and manual I have just state 'make config'. Eh? :mad:

[Tyr-7BE]

You don't need patches if you download the 2.4.3 source as you did. Patches are used to either upgrade 2.4.2 to 2.4.3 (or a similar increment...2.2.x won't patch to 2.4.x), or to make minor adjustments to the kernel (eg, better support for ReiserFS). You should be just find downloading the source.
Now you've untarred the file, you've cd linux 'd, and you've typed "make mrproper" (it basically executes a script that makes sure that there's nothing lying around the linux directory that will interfere with the compile). Now try typing "make xconfig". You must have an X window session running in order to use this, but it's much more user friendly than both config and menuconfig. From the beginning, this is pretty much the only syntactical stuff you should do if you're using make xconfig or menuconfig:

make mrproper
make xconfig (or "menuconfig" or even "config")
make deps
make bzImage
make modules
make modules_install

That's if all goes well...kernel compilation can sometimes be a big step, but it's by no means unachievable. Good luck :)

[ 09 April 2001: Message edited by: Tyr-7BE ]

[pika_pika]

Wow, would've loved to say xconfig worked, but it gave the same error within kde. I was going to post anyhow to ask you what that error meant even if xconfig worked but now I don't even have to bother as neither 3 of those work. I hope it's something simple and stupid I'm doing! ;)

[pika_pika]

Check out how retarded this was. It was just because I wasn't in the linux directory. DUH! Oh well, learn the hard way.

Anyhow, now I have a new question that is probably just as lame.