Re: WITHOUT_PF breaks buildworld
- Reply: Gary Jennejohn : "Re: WITHOUT_PF breaks buildworld"
- Reply: Kristof Provost : "Re: WITHOUT_PF breaks buildworld"
- In reply to: Gary Jennejohn : "Re: WITHOUT_PF breaks buildworld"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 22 Dec 2021 07:21:35 UTC
Hi, I think the reason is somewhere in tools/build/test-includes: --- net/if_pfsync.o --- In file included from net/if_pfsync.c:1: In file included from [...]freebsd/arm64.aarch64/tmp/usr/include/net/if_pfsync.h:56: [...]freebsd/arm64.aarch64/tmp/usr/include/net/pfvar.h:65:10: fatal error: 'netpfil/pf/pf.h' file not found #include <netpfil/pf/pf.h> ^~~~~~~~~~~~~~~~~ 1 error generated. *** [net/if_pfsync.o] Error code 1 make[3]: stopped in [...]freebsd/tools/build/test-includes --- net/pfvar.o --- In file included from net/pfvar.c:1: [...]freebsd/arm64.aarch64/tmp/usr/include/net/pfvar.h:65:10: fatal error: 'netpfil/pf/pf.h' file not found #include <netpfil/pf/pf.h> ^~~~~~~~~~~~~~~~~ 1 error generated. *** [net/pfvar.o] Error code 1 make[3]: stopped in [...]freebsd/tools/build/test-includes 2 errors make[3]: stopped in [...]freebsd/tools/build/test-includes *** [test-includes] Error code 2 make[2]: stopped in [...]freebsd 1 error Best regards, Konrad Sewiłło-Jopek niedz., 19 gru 2021 o 12:26 Gary Jennejohn <gljennjohn@gmail.com> napisał(a): > On Sun, 19 Dec 2021 19:05:35 +0800 > Alastair Hogge <agh@riseup.net> wrote: > > > On Sunday, 19 December 2021 6:47:23 PM AWST Gary Jennejohn wrote: > > > Some recent change, probably in a .mk file, breaks builworld on HEAD > > > when WITHOUT_PF is enabled in src.conf. > > > > I have had to disable WITHOUT_PF since 2020-07-27, but probably earlier. > > > > Hmm. I did a successful buildworld a few days ago with WITHOUT_PF > enabled, so it's new breakge for me at least. > > I don't enable pf in the kernel and don't need it in userland. > > > > Disabling WITHOUT_PF results in a successful buildworld. > > > > > > The reported error is that netpfil/pf/pf.h can't be found. > > > > Some ports depend on that too. > > > > It may not be a problem for ports. Depends on where they look for > it. The file is still there under /sys and /usr/include. > > -- > Gary Jennejohn > >