On Sat, Sep 06, 2025 at 02:59:25PM +0200, Michael Tuexen wrote: > > On 6. Sep 2025, at 10:31, Bjoern A. Zeeb <bzeeb-li...@lists.zabbadoz.net> > > wrote: > > > > On Sat, 6 Sep 2025, Michael Tuexen wrote: > > > >> OK, that is fixed in > >> https://cgit.FreeBSD.org/src/commit/?id=7c448f5aab8be6977d0860e608e7d497b495d28c > >> > >> <https://cgit.freebsd.org/src/commit/?id=7c448f5aab8be6977d0860e608e7d497b495d28c> > > > > Thanks! > > > >> Thanks again for reporting and I am sorry for breaking the NOIP (again). > >> BTW: Is there a reason we don't have the NOINET, NOINET6, and NOIP kernel > >> configs for arm64? > > > > I think initially we only added all the extra kernel configs 10-15 years > > ago to amd64 as that was the fastest way to build a universe (for a > > target). I am likely guilty for NOINET and VIMAGE and NOIP... > > initially generating them if I do not misremember. > > > > Adding them to a 2nd arch would increase full make universe build times but > > given a lot of people have started to do native builds on higher core arm64 > > machines I wonder if it would be time to add them there? > Does adding a kernel config also requires it to activate it in make universe? > arm64 is now tier one and I use arm64 platforms more often then amd64 for > development.
I believe adding a new config to sys/arm64/conf will automatically cause it to be included in universe builds. > > I'll Cc: source manager and see how they feel about this... I don't see any particular problem with building the extra kernels on arm64 as well. It might be useful to build-test NOIP etc. configurations with "options FDT". But even if one is using arm64 for development, it's trivial to build the corresponding amd64 kernels when build-testing, just set TARGET.
