Date: Tue, 23 Jun 2020 13:39:38 +0300 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: John Baldwin <jhb@FreeBSD.org>, Mark Johnston <markj@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r362338 - in head: share/man/man4 sys/conf sys/kern sys/netinet sys/netinet6 sys/netipsec sys/netpfil/pf Message-ID: <271824e9-3454-e6fd-8bb0-c3c032832b26@yandex.ru> In-Reply-To: <5fcb4de8-f4a6-54b4-067c-058bf2b43871@FreeBSD.org> References: <202006181932.05IJWZYH009560@repo.freebsd.org> <aebe7273-fab4-363a-6f51-6d934cf37186@FreeBSD.org> <20200622011035.GG85944@raichu> <cbbab0d0-a91e-f9d8-1a5d-33ba3f36c26d@FreeBSD.org> <20200622220752.GB51374@raichu> <5fcb4de8-f4a6-54b4-067c-058bf2b43871@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23.06.2020 01:20, John Baldwin wrote: >> I tend to assume that a buildkernel of GENERIC without any special flags >> will always build all modules (except those not available for the target >> platform of course), so I was a bit surprised to see that this isn't the >> case for ipsec.ko. As Rodney pointed out it provides marginally better >> coverage against build breaks. If you think we can restore the old >> behaviour for ipsec without too much work I think it'd be reasonable to >> change that and compile sctp.ko even when "options SCTP" is configured. >> I can't spot any similar cases in sys/modules/Makefile with a bit of >> skimming. > > I don't think ipsec.ko is easily fixable when I looked at it. I think it > is fine to leave sctp.ko building as part of GENERIC though. Hi, I'm sorry, I missed these changes, but in the past there weren't any problems in building ipsec.ko module with/without any possible options. I'll try to look what happened and what can be do to fix this at the weekend. -- WBR, Andrey V. Elsukov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?271824e9-3454-e6fd-8bb0-c3c032832b26>