On Tuesday 10 December 2002 5:02 am, zentara wrote:
On Mon, 09 Dec 2002 17:07:46 -0800
Tom Emerson <osnut@pacbell.net> wrote:
make[1]: Leaving directory `/usr/src/linux-2.4.19.SuSE/arch/i386/kernel' make: *** [_dir_arch/i386/kernel] Error 2
So, have I stepped in the goo on this? should I back up an redo the "make cloneconfig" and try that [without any additional 'diddling'] or is there simply "a problem" with the latest kernel sources "as supplied" by SuSE and I'm stuck unless *I* want to investigate and repair... [yeah, RIGHT!]
If you are going to do a cloneconfig of suse, you need to apply all their patches to the kernel.
pardon my dumb look, but I thought that that is what I downloaded -- SuSE's "patched" 2.4.19 kernel. OTOH, this is the first time I've tried "cloneconfig" -- I didn't even know such a beast existed until I started scanning this group...
You probably will have to skip make cloneconfig, and go thru each config option and read the help, and decide if you need it. Then save your new custom config.
That is what I originally intended to do, but it seems the interdependancy level has "grown" considerably with later kernels. Not so much of "this kernel element needs that component", but rather "this program used during the boot process needs module xxx to be installed" [and, of course, that program is never heard from again...] I realize SuSE makes what I call a "kitchen sink" kernel build [everything, including the kitchen sink, is in there somehow...] and I understand why they would need to do this: they have no clue as to what hardware *I* actually have (or intend to use), and anything I have or want to use WILL differ radically from what my neighbor has or wants... It would be really great if someone could come up with a program to scan your actual hardware and build a .config file to match [hmm, "make yourconfig"?] and [possibly seperately] ask about "optional" items [not hardware related; things like which file system to use, or raid support, etc.] To then base a distribution's installation on such would be icing on the cake (i.e., the install process probes the system, builds a custom kernel configuration, and compiles the kernel as a matter of course...) Mind you, this wouldn't be a "consumer" level distribution -- perhaps the ultimate "professional/server" distribution instead...