After reading various README's and HOWTO's, I'm attempting to compile kernel 2.6.5 from my home directory, without logging on as "root." In one place the 2.6.XX README says:
- If you install the full sources, put the kernel tarball in a
directory where you have permissions (eg. your home directory) and
gzip -cd linux-2.6.XX.tar.gz | tar xvf -
Replace "XX" with the version number of the latest kernel.
Do NOT use the /usr/src/linux area! This area has a (usually
incomplete) set of kernel headers that are used by the library header
files. They should match the library, and not get messed up by
whatever the kernel-du-jour happens to be.
So, I did that and then
This is a small sample of the configuration window
OOOOOO OOOO OOOOOO OOOO OOOOO OOOO OOOOOOOOOOOO OOOOOOOO
oooooo oooo oooooo oo ooo ooooo oooo ooooo oooooooo ooo ooooooo oooo oooo oo
all is well.
Now when I unpack the tarball in /usr/src/ and run the same commands, everything is fine with make xconfig
Another part of the README says:
When compiling the kernel all output files will per default be
stored together with the kernel source code.
Using the option "make O=output/dir" allow you to specify an alternate
place for the output files (including .config).
kernel source code: /usr/src/linux-2.6.N
build directory: /home/name/build/kernel
To configure and build the kernel use:
make O=/home/name/build/kernel menuconfig
sudo make O=/home/name/build/kernel modules_install install
Please note: If the 'O=output/dir' option is used then it must be
used for all invocations of make.
The use of the reference to /usr/src/ confuses me based on the first quote from the README. To the point of this quote--I haven't tried it yet--if I use the make 0=
option, the way I read this, is that the kernel will be installed in my home directory. I don't want that.
Here is what I'm asking:[list=1][*]What's causing the gibberish when I <make xconfig> from my home directory?[*]Will using the <make 0=> option install both the kernel--bzImage, vmliuz--and the modules in the directories where they usually go--/boot/ and /lib/modules?[/list=1]
It would be easier just to "cave in" and build from /usr/src/ as root, but I don't want to concede defeat.