Re: kernel compile fails if device bpf is not enabled

> On Feb 8, 2023, at 2:32 PM, Gary Jennejohn wrote: > > On Wed, 8 Feb 2023 12:49:46 +0800 > Zhenlei Huang mailto:z...@freebsd.org>> wrote: > > Hi Zhenlei, > >> Thanks for the report! Post the fix to Phabricator >> https://reviews.freebsd.org/D38432 >>

Re: kernel compile fails if device bpf is not enabled

On Wed, 8 Feb 2023 12:49:46 +0800 Zhenlei Huang wrote: Hi Zhenlei, > Thanks for the report! Post the fix to Phabricator > https://reviews.freebsd.org/D38432 . > > Best regards, > Zhenlei > Thanks! I see it's been accepted. > > On Feb 7, 2023, at 5:08 PM,

Re: kernel compile fails if device bpf is not enabled

Hi Gary, Thanks for the report! Post the fix to Phabricator https://reviews.freebsd.org/D38432 . Best regards, Zhenlei > On Feb 7, 2023, at 5:08 PM, Gary Jennejohn wrote: > > I just saw this error today because I didn't have device bpf enabled in > my kern

kernel compile fails if device bpf is not enabled

I just saw this error today because I didn't have device bpf enabled in my kernel configuration file: -- >>> stage 3.1: building everything -- linking kernel.full ld: error: unde

Re: kernel compile fails in uma_core.c

On Sun, 30 Nov 2003, Paulius Bulotas wrote: > Hello, > > when building kernel: > ../../../vm/uma_core.c: In function `zone_timeout': > ../../../vm/uma_core.c:345: error: `mp_maxid' undeclared (first use in > this function) > and so on. > > Anything I missed? I just fixed this, sorry. > > Pauliu

Re: kernel compile fails in uma_core.c

On Sun, 30 Nov 2003, Paulius Bulotas wrote: > Hello, > > when building kernel: > ../../../vm/uma_core.c: In function `zone_timeout': > ../../../vm/uma_core.c:345: error: `mp_maxid' undeclared (first use in > this function) > and so on. > > Anything I missed? No, this is the "bad" commit for UP b

kernel compile fails in uma_core.c

Hello, when building kernel: ../../../vm/uma_core.c: In function `zone_timeout': ../../../vm/uma_core.c:345: error: `mp_maxid' undeclared (first use in this function) and so on. Anything I missed? Paulius ___ [EMAIL PROTECTED] mailing list http://lists

Re: 5.1 - stl Kernel compile fails

David O'Brien wrote: On Wed, Oct 29, 2003 at 08:11:53AM +0100, Karl M. Joch wrote: On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote: i added a stallion easy i/o to a 5.1 box. compiling the kernel fails with a lot of errors in stallion.c. any chance that this gets corrected soon? I

Re: 5.1 - stl Kernel compile fails

On Wed, Oct 29, 2003 at 08:11:53AM +0100, Karl M. Joch wrote: > >On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote: > > > >>i added a stallion easy i/o to a 5.1 box. compiling the kernel fails > >>with a lot of errors in stallion.c. any chance that this gets corrected > >>soon? > > > >

Re: 5.1 - stl Kernel compile fails

David O'Brien wrote: On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote: i added a stallion easy i/o to a 5.1 box. compiling the kernel fails with a lot of errors in stallion.c. any chance that this gets corrected soon? Is this an ISA or PCI card? it is an easy i/o 8 PCI card. i hav

Re: 5.1 - stl Kernel compile fails

On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote: > i added a stallion easy i/o to a 5.1 box. compiling the kernel fails > with a lot of errors in stallion.c. any chance that this gets corrected > soon? Is this an ISA or PCI card? ___ [EMAI

Re: 5.1 - stl Kernel compile fails

On Tue, Oct 28, 2003 at 12:21:09PM +0100, Karl M. Joch wrote: > Kris Kennaway wrote: > > >On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote: > > > >>i added a stallion easy i/o to a 5.1 box. compiling the kernel fails > >>with a lot of errors in stallion.c. any chance that this gets co

Re: 5.1 - stl Kernel compile fails

Kris Kennaway wrote: On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote: i added a stallion easy i/o to a 5.1 box. compiling the kernel fails with a lot of errors in stallion.c. any chance that this gets corrected soon? Post the errors you're seeing so we don't have to guess. Kris

Re: 5.1 - stl Kernel compile fails

On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote: > i added a stallion easy i/o to a 5.1 box. compiling the kernel fails > with a lot of errors in stallion.c. any chance that this gets corrected > soon? Post the errors you're seeing so we don't have to guess. Kris pgp0.pgp Des

5.1 - stl Kernel compile fails

i added a stallion easy i/o to a 5.1 box. compiling the kernel fails with a lot of errors in stallion.c. any chance that this gets corrected soon? -- Best regards / Mit freundlichen Gruessen, Karl M. Joch http://www.freebsd.at - Das Power Betriebssystem

Re: kernel compile fails...

On Mon, 7 Jan 2002, John Baldwin wrote: > You must have cvsup'd at a bad time. I removed SWI_NOSWITCH from cam and > everywhere else in one big commit Friday or Saturday. I have other problems with the cvsup upgrade from STABLE to CURRENT on my machine. One of em is that my machine won't go p

Re: kernel compile fails...

On 06-Jan-02 Emiel Kollof wrote: > On Sun 06 Jan 02 06:54, Makoto Matsushita wrote: >> coolvibe> What header file defines SWI_NOSWITCH? >> >> http://snapshots.jp.freebsd.org/tour/current/cgi-bin/global.cgi?pattern=SWI >>_NOSWITCH&id=&type=symbol >> >> SWI_NOSWITCH are used and/or defined by these

Re: kernel compile fails...

On Sun 06 Jan 02 06:54, Makoto Matsushita wrote: > coolvibe> What header file defines SWI_NOSWITCH? > > http://snapshots.jp.freebsd.org/tour/current/cgi-bin/global.cgi?pattern=SWI >_NOSWITCH&id=&type=symbol > > SWI_NOSWITCH are used and/or defined by these files. You can easily > find that this l

Re: kernel compile fails...

coolvibe> What header file defines SWI_NOSWITCH? http://snapshots.jp.freebsd.org/tour/current/cgi-bin/global.cgi?pattern=SWI_NOSWITCH&id=&type=symbol SWI_NOSWITCH are used and/or defined by these files. You can easily find that this list have only one *.h file -- sys/sys/interrupt.h. % grep S

kernel compile fails...

I upgraded a STABLE machine to CURRENT and while compiling the kernel for the first time, it barfed here: /usr/src/sys/cam/cam_xpt.c: In function `xpt_done': /usr/src/sys/cam/cam_xpt.c:4765: `SWI_NOSWITCH' undeclared (first use in this fu nction) /usr/src/sys/cam/cam_xpt.c:4765: (Each undeclared

Re: kernel compile fails in: ../../dev/vx/if_vx_pci.c

On Fri, 26 May 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> The Hermit >Hacker writes: > : make depend went through no probs, but a make fails at: > > You may have overlooked this entry in UPDATING: > > 2319: > The ISA and PCI compatability shims have been connected to t

Re: kernel compile fails in: ../../dev/vx/if_vx_pci.c

In message <[EMAIL PROTECTED]> The Hermit Hacker writes: : make depend went through no probs, but a make fails at: You may have overlooked this entry in UPDATING: 2319: The ISA and PCI compatability shims have been connected to the options COMPAT_OLDISA and COMPAT_OLDPCI. I

kernel compile fails in: ../../dev/vx/if_vx_pci.c

Just decided to brave going from 4.0->5.0 ... upgraded all my sources, checked over the UPGRADING file, GENERIC and LINT, to see if anyting pop'd out as far as changing my config is concerned ... make depend went through no probs, but a make fails at: cc -c -O3 -mpentium -pipe -Wall -Wredundant

Re: Current kernel compile fails

On Sat, 18 Dec 1999, Manfred Antar wrote: !>I think this happened when mbuf.h was changed : !> !>linking kernel.debug !>uipc_mbuf.o: In function `m_mballoc_wait': !>/sys/compile/pro2/../../kern/uipc_mbuf.c(.text+0x2cb): undefined reference !>to `m_mballoc_wakeup' !>uipc_mbuf.o: In function `m_cl

Current kernel compile fails

I think this happened when mbuf.h was changed : linking kernel.debug uipc_mbuf.o: In function `m_mballoc_wait': /sys/compile/pro2/../../kern/uipc_mbuf.c(.text+0x2cb): undefined reference to `m_mballoc_wakeup' uipc_mbuf.o: In function `m_clalloc_wait': /sys/compile/pro2/../../kern/uipc_mbuf.c:349