1 |
On 4/15/20 1:40 PM, Andreas Stiasny wrote: |
2 |
> On 15.04.20 17:50, Rich Freeman wrote: |
3 |
|
4 |
>> Jumping from |
5 |
>> 3.18 you're somewhat more likely to run into issues - your biggest |
6 |
>> headache though will be dealing with the 30,000 prompts you get from |
7 |
>> make oldconfig and making sure you set all the new options correctly. |
8 |
|
9 |
> That's why I use make olddefconfig in such a case. This takes all the |
10 |
> old config values and uses the default for the new ones. If you know |
11 |
> that you need one or more of the new config options you can fine tune |
12 |
> them afterwards with make menuconfig. |
13 |
|
14 |
|
15 |
> Andreas |
16 |
|
17 |
james responded: |
18 |
|
19 |
> Ah. never used olddefconfig, I'll give it a spin. |
20 |
|
21 |
That raises the question, what if you have no kernel config, as may be the case if you are going to Gentoo for the first time, or are cross-compiling from FreeBSD or NetBSD? |
22 |
|
23 |
I have tried with OpenADK (www.openadk.org), which got as far as successfully building cross-gcc some of the time, but never succeeded at building the kernel. |
24 |
|
25 |
Is defconfig the best starting point? One would want to maximize the probability of success building the kernel while retaining a functional system that would support vital hardware including ethernet, wi-fi, hard drives and USB, and I would need to be able to read a NetBSD or FreeBSD file system (UFS/FFSv1 or 2). I use GPT, so there are no traditional now-deprecated BSD disklabels that Linux would not recognize. |
26 |
|
27 |
If I just start with menuconfig, I could miss some vital parts. |
28 |
|
29 |
OpenADK started with a minimal kernel config, maybe it was too minimal? |
30 |
|
31 |
I have successfully compiled kernels and userlands on FreeBSD and NetBSD (no menuconfig, defconfig, etc; kernel configs start with a GENERIC config). NetBSD kernel config is much longer than FreeBSD kernel config but is dwarfed by Linux kernel config. |
32 |
|
33 |
Tom |