Thomas Mueller
2016-Dec-12 09:07 UTC
make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf
> BUILDKERNELS=PUMPKIN GENERIC> > to your /etc/src.conf and removing the KERNCONF line from /etc/make.conf > > before you run it again. KERNCONF goes on the "make buildkernel" command, > > not into /etc/make.conf, but should not be necessary at all if /etc/src.conf > > contains the list of kernels to be built. (See src.conf(5).)> - BUILDKERNELS is used in Makefile.inc1 but not listed in neither > src.conf(5) nor make.conf(5) > - KERNCONF is listed in make.conf(5) > - I use KERNCONF in /etc/make.conf to build two kernels and it works> So why are you giving this advice?> HerbertI would have thought KERNCONF would belong in src.conf, but just checked the man pages, and KERNCONF is listed in man make.conf but not src.conf . I usually build at least two kernels, one being the custom kernel and the other being GENERIB. GENERIB differs from GENERIC in not supporting very outdated devices (ISA SCSI cards for instance) but including support from some wi-fi drivers not in GENERIC. I need rsu. My question is, do you build modules redundantly, or just once? I don't want to build the same modules more than once. Tom
tech-lists
2016-Dec-12 09:16 UTC
make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf
On 12/12/2016 09:07, Thomas Mueller wrote:> My question is, do you build modules redundantly, or just once? > I don't want to build the same modules more than once.For me - redundantly, I guess. It's not like it takes a lot of time or space on the compiling machine, and I ensure that everything that needs to be built, is built. PUMPKIN = heavily modified config with all the stuff I don't need stripped out, and a couple of non-default lines. GENERIC = unmodified kernel that should work if by some chance PUMPKIN doesn't. -- J.