On Tue, 29 Nov 2011 10:05:11 +0100 "T. Valent" wrote: > `fpu_mxcsr_mask' > > The above line is just an example. I have poked around with more or less > guessing what could be missing, but after 2 days I'm quite sure I need a > general solution to finding the dependencies instead of guessing. > > I have no skills in kernel coding. I wonder if there's a good way to > find out which part I am missing in the config file(s).
The output from the build is usually quite good and clear more so than ports as to what is missing and working out what you can turn off is usually more related to hardware knowledge. I get the kernel down to 2Meg and running fine. Used to be a little less but the kernels grown quite a lot since then. Here's a trick I learnt from faulty unit mods in Total Annihilation when I was young and have used once on the OpenBSD kernel configs. Far better than pulling a unit out or adding one by one especially when twenty are broke. Split your config in half, choose the half you think is most likely to cause the problem and diff that half back to defaults and compile. If it works try the other half, if it doesn't split in half again, eventually you'll have a ureka moment sometimes almost immediately or possibly after finding there's more than one problem breaking the build and causing a bit of head scratching and a bit more work just when you thought you were getting near. You get the jist anyway, split and consider. The configs are far smaller and easier to use than Linux :-)
