Ian Lepore skrev:
>
> On Tue, 2016-12-13 at 10:13 -0700, Ian Lepore wrote:
>> On Tue, 2016-12-13 at 10:00 +, tech-lists wrote:
>> >
>> > On 12/12/2016 23:40, Herbert J. Skuhra wrote:
>> > >
>> > >
>> > > PORTS_MODULES does not work if KERNCONF contains multiple
>> > > kernels:
>> > >
>> >
On Tue, 2016-12-13 at 10:13 -0700, Ian Lepore wrote:
> On Tue, 2016-12-13 at 10:00 +, tech-lists wrote:
> >
> > On 12/12/2016 23:40, Herbert J. Skuhra wrote:
> > >
> > >
> > > PORTS_MODULES does not work if KERNCONF contains multiple
> > > kernels:
> > >
> > > The problem is obviously in
On Tue, 2016-12-13 at 10:00 +, tech-lists wrote:
> On 12/12/2016 23:40, Herbert J. Skuhra wrote:
> >
> > PORTS_MODULES does not work if KERNCONF contains multiple kernels:
> >
> > The problem is obviously in /usr/src/sys/conf/kern.post.mk (line
> > 66):
> >
> > WRKDIRPREFIX?=
On Mon, 2016-12-12 at 20:22 -0800, Kevin Oberman wrote:
> On Mon, Dec 12, 2016 at 4:20 PM, Herbert J. Skuhra rg>
> wrote:
>
> >
> > Kevin Oberman skrev:
> > >
> > >
> > > Clearly the documentation is a bit behind the times. For some
> > > time people
> > > have used
On 12/12/2016 23:40, Herbert J. Skuhra wrote:
PORTS_MODULES does not work if KERNCONF contains multiple kernels:
The problem is obviously in /usr/src/sys/conf/kern.post.mk (line 66):
WRKDIRPREFIX?= ${MAKEOBJDIRPREFIX}${SRC_BASE}/sys/${KERNCONF}
hmm! I didn't know that.
I can't confirm
On 13/12/2016 04:22, Kevin Oberman wrote:
I should also mention that, if you want to install a new kernel without
overwriting the old kernel and modules (/boot/kernel.old/), "make
reinstallkernel". It replaces the existing kernel instead of renaming the
kernel directory to kernel.old. I find
Kevin Oberman skrev:
>
> On Mon, Dec 12, 2016 at 4:20 PM, Herbert J. Skuhra
> wrote:
>
>> Kevin Oberman skrev:
>> >
>> > Clearly the documentation is a bit behind the times. For some time people
>> > have used KERNCONF to build multiple kernels, but that was a lucky things
On Mon, Dec 12, 2016 at 4:20 PM, Herbert J. Skuhra
wrote:
> Kevin Oberman skrev:
> >
> > Clearly the documentation is a bit behind the times. For some time people
> > have used KERNCONF to build multiple kernels, but that was a lucky things
> > that was not officially
Kevin Oberman skrev:
>
> Clearly the documentation is a bit behind the times. For some time people
> have used KERNCONF to build multiple kernels, but that was a lucky things
> that was not officially supported. It just happened to work. Then, with
> 11.0, it no longer did in many cases sue to
Kevin Oberman skrev:
>
> On Mon, Dec 12, 2016 at 1:16 AM, tech-lists wrote:
>> 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 -
tech-lists skrev:
>
> Hi,
>
> Yep I'm sure. The only extra I've added is for
> nvidia-driver. Everything else is a "without" directive. My
> /etc/src.conf looks like this:
>
> # less src.conf
> PORTS_MODULES=x11/nvidia-driver
> [...]
> This is the error I get when I try to build kernel and
On Mon, Dec 12, 2016 at 1:16 AM, tech-lists wrote:
> 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
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
> 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
Scott Bennett skrev:
>
> On Sun, 11 Dec 2016 12:34:58 + tech-lists
> wrote:
>
>> I have found that make buildkernel/installkernel does not respect
>> KERNCONF= variables. It also doesn't respect MAKE_JOBS_NUMBER. It *DOES*
>> however respect WITH_CCACHE_BUILD.
On Sun, 11 Dec 2016 12:34:58 + tech-lists
wrote:
>I have found that make buildkernel/installkernel does not respect
>KERNCONF= variables. It also doesn't respect MAKE_JOBS_NUMBER. It *DOES*
>however respect WITH_CCACHE_BUILD. It's hard to say when the behaviour
On 11/12/2016 16:48, Herbert J. Skuhra wrote:
tech-lists wrote:
Hello list,
I have found that make buildkernel/installkernel does not respect
KERNCONF= variables. It also doesn't respect MAKE_JOBS_NUMBER. It
*DOES* however respect WITH_CCACHE_BUILD. It's hard to say when the
behaviour changed
tech-lists wrote:
>
> Hello list,
> I have found that make buildkernel/installkernel does not respect
> KERNCONF= variables. It also doesn't respect MAKE_JOBS_NUMBER. It
> *DOES* however respect WITH_CCACHE_BUILD. It's hard to say when the
> behaviour changed to what it is, but it was sometime
Hello list,
I have found that make buildkernel/installkernel does not respect
KERNCONF= variables. It also doesn't respect MAKE_JOBS_NUMBER. It *DOES*
however respect WITH_CCACHE_BUILD. It's hard to say when the behaviour
changed to what it is, but it was sometime around the time that
19 matches
Mail list logo